fix(ci): align npm dist-tags with GA releases#143
Open
kadel wants to merge 4 commits into
Open
Conversation
Publishing from main now uses the `next` dist-tag instead of `latest`. The `latest` tag is reserved for the auto-detected highest semver release branch (e.g., release-1.10), matching the convention used for catalog images and quay tags. Older release branches continue to use their branch name as the dist-tag. Assisted-by: Claude Code
Assisted-by: Claude Code
nickboldt
reviewed
Jul 17, 2026
Address PR review feedback: explicitly pass --tag latest for the highest GA branch and add a separate npm dist-tag for the branch name so the package is discoverable via both tags. Assisted-by: Claude Code
Assisted-by: Claude Code
|
kadel
marked this pull request as ready for review
July 20, 2026 15:50
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
3 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.
Summary
mainnow uses--tag nextinstead oflatestlatestdist-tag is reserved for the auto-detected highest semver release branch (e.g.,release-1.10), matching the convention used for catalog images and quay tagsrelease-1.9) continue to use their branch name as the dist-tagHow it works
A new "Detect latest GA branch" step uses
git ls-remoteto list allrelease-*branches, sorts them numerically by semver, and picks the highest one. The publish step then:main→npm publish --tag nextnpm publish(defaults tolatest)npm publish --tag <branch-name>After merge
Run the publish workflow once from
release-1.10to reclaim thelatesttag from the current 1.11.x pointer.Test plan
release-1.10→ should publish aslatestmain→ should publish asnextrelease-1.9→ should publish asrelease-1.9