Surface stale latest dist-tag drift in Stage B; document pre-stable retarget - #68
Merged
Merged
Conversation
…et step npm force-creates `latest` on a package's first publish even under --tag alpha, never moves it, and won't allow deleting it — so `latest` froze on 0.1.0-alpha.1 while `alpha` advanced to alpha.2. OIDC trusted publishing cannot run dist-tag mutations (publish-only credentials), so Stage B now emits a warning + step-summary line with the exact retarget command when `latest` lags the released version, and the release process documents keeping `latest` on the newest prerelease (manual, interactive npm login) until a stable 0.1.0 ships with --tag latest. Claude-Session: https://claude.ai/code/session_01LjqCaCwPby6EGi4RmBVtEW
Sentinel dependency audit — WARN · ✓ ok137 allow · 12 warn · 0 block · 0 error
▶ Run Sentinel · 149 packages audited · 2026-07-14T06:15:06.035Z · SBOM uploaded as a build artifact |
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
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.
npm auto-created
latest→ 0.1.0-alpha.1 on first publish (its standard behavior even with--tag alpha) and never moves it, so a plainnpm installcurrently resolves to the older alpha. OIDC trusted publishing can't mutate dist-tags, so Stage B now warns (with the exact command) whenlatestis stale, and docs/release-process.md documents keepinglateston the newest prerelease until stable 0.1.0 ships with--tag latest.Immediate registry fix (manual, one-time per release):
for p in core proxy sandbox mcp steward cli action; do npm dist-tag add "@git-agentic/sentinel-$p@0.1.0-alpha.2" latest; donehttps://claude.ai/code/session_01LjqCaCwPby6EGi4RmBVtEW