fix(release): verify propagation in rounds instead of per package - #9
Merged
Conversation
Release verification - Re-read the dist-tag in rounds over the packages still pending, so waiting on one straggler re-reads the rest for free - Budget ten rounds of linear backoff, three minutes in total however many packages lag; per-package it multiplied by the number of stragglers and overran the release job's own timeout - Say in the failure that a tag serving the PREVIOUS version is propagation lag rather than a failed publish, and name the re-check - Controlled against a fake registry lagging two of ten packages by 30s after their own publish; the previous per-package form reddens on one of them under the same fake Documentation and comments - Reframe the bootstrap section as adding a package to the published set, since trusted publishing is configured per package and the procedure recurs - Correct its instruction to publish with a token from CI: the workflow is OIDC-only and its preflight rejects a token, so a new package's first publish has to be local under npm login - Replace two comments that outlived their facts, the workflow's bootstrap justification and a marker tag this repository has never carried Allow CI to be dispatched from the UI, since a branch with no open pull request matches neither existing trigger. - Add workflow_dispatch to ci.yml, wired to nothing Relates to #7
martin-fleck-at
force-pushed
the
issues/7-verify-propagation
branch
from
September 9, 2026 08:58
e0254a0 to
6ffb517
Compare
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
1 participant
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.
Relates to #7