Skip to content

ci(release): point npm next dist-tag at final releases - #2

Merged
shixish merged 1 commit into
mainfrom
ci/next-tag-follows-latest
Nov 18, 2026
Merged

shixish merged 1 commit into
mainfrom
ci/next-tag-follows-latest

Conversation

@shixish

@shixish shixish commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

When a final (non-prerelease) version is published, also run npm dist-tag add <pkg>@<version> next, so next is never behind latest. Prereleases are unchanged (they already publish under next).

  • Auth is npm trusted publishing (OIDC) only, no token. npm docs now support npm dist-tag over OIDC, which needs npm >= 11.21.0 / 12.2.0 (the workflow already installs a new enough npm) and "Allow npm dist-tag" enabled on the package's trusted publisher at npmjs.com (off by default).
  • The step runs after publish and only on real tag pushes. If the permission isn't enabled yet it emits a ::warning:: with the manual command and does not fail the release, since the version is already published.
  • Re-running a release after the publish already succeeded still repoints next.

🤖 Generated with Claude Code

Keeps next from falling behind latest. Uses OIDC trusted publishing for npm dist-tag; warns instead of failing if the permission is not enabled.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@shixish
shixish merged commit 615b3ff into main Nov 18, 2026
9 checks passed
@shixish
shixish deleted the ci/next-tag-follows-latest branch November 18, 2026 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant