docs: document the publish window on the versioning page (fixes #2974) - #2996
Merged
Conversation
A release publishes the packages one after another, so during the run the registry holds the new version for some `@mittwald/flow-*` packages and not yet for others — ~25 minutes for the 1.0.6 release. A consumer who moves all their Flow dependencies to one version in that window gets ETARGET with nothing to indicate that waiting fixes it. Hitting the window is likely rather than exotic: all packages share one version, and `@mittwald/flow-react-components` declares `@mittwald/flow-icons-pro` as a peer at an exact version, so an update always spans several packages. The section names the error, says it resolves itself, and says that no pinning workaround is needed or wanted. The matching sentence in flow-codemods' README is deliberately left out: neither the README nor the `upgrade` CLI exists on main — both live on #2978, which is where that sentence has to ride along. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Coverage Report for ./packages/components/
File CoverageNo changed files found. |
Contributor
🚀 Preview DeploymentPreview environments are ready:
Images:
|
Lisa18289
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Flow's packages are not published at the same moment — Lerna publishes them one
after another, so during a release run the registry holds the new version for
some
@mittwald/flow-*packages and not yet for others. During the1.0.6release that window was ~25 minutes. A consumer who moves all their Flow
dependencies to one version in it gets
ETARGETwith nothing to indicate thatwaiting fixes it.
This is not a publish hole (#2887, closed as accepted) — it is only about
telling users. The new „Direkt nach einem Release" section on the
versioning page does that:
differ for a few minutes;
version, and
@mittwald/flow-react-componentsdeclares@mittwald/flow-icons-proas a peer at an exact version, so an updatealways spans several packages;
ETARGET/ERR_PNPM_NO_MATCHING_VERSION);is needed and none is wanted.
Left out on purpose
The issue also asks for a sentence in
flow-codemods' README. Neither theREADME nor the
upgradeCLI exists onmain— both live on #2978. Thesentence has to ride along there, or it collides on merge.
Verification
direkt-nach-einem-release, the codeblock and the
Alertrender, and the following Component Lifecycle sectionis intact.
pnpm format:checkandpnpm nx test:links docsgreen.fixes #2974
🤖 Generated with Claude Code