ci: one canonical registry-serve check, shared by all ten repositories - #31
Merged
Conversation
`sshlg-skills@1.48.1` went red on "The registry must actually serve it" while the publish had succeeded — `+ sshlg-skills@1.48.1`, provenance signed — and the version was served minutes later. npm warns on every publish that a package "may take a few minutes to become available"; the check waited three. The fix had existed in `telegram-dev` since 2026-08-25 and reached none of the other nine: ten minutes instead of three, and the two failure cases told apart, because "the registry does not know this package" and "it does not serve this version" need different answers. A second defect surfaced in the same pass, one telegram-dev had not hit: the poll asked for the latest dist-tag rather than for the version. Both halves are now one step, byte-identical in all ten, comment included. The rule the two incidents argue for is written down in the umbrella — `docs/working-rules/shared-mechanism-propagation.md`: a shared mechanism is fixed in every copy, in the same change, or it is not fixed. Verification: YAML parses; npm test EXIT=0 in this repository. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
sshlg-skills@1.48.1went red on "The registry must actually serve it" while the publish had succeeded — the version was served minutes later. npm warns on every publish that a package "may take a few minutes to become available"; the check waited three.The fix had existed in
telegram-devsince 2026-08-25 and reached none of the other nine. A second defect surfaced in the same pass, one telegram-dev had not hit: the poll askednpm view <name> version— the latest dist-tag, not the version. Those differ while the tag lags, and differ permanently for a patch published behind a newer minor.Each repository held half the knowledge. Both halves are now one step, byte-identical in all ten.
The rule is recorded in the umbrella as
docs/working-rules/shared-mechanism-propagation.md: a shared mechanism is fixed in every copy, in the same change, or it is not fixed.Verification: YAML parses;
npm testEXIT=0 here.🤖 Generated with Claude Code