Skip to content

ci(publish): stage prerelease tags on npm next and mark them prerelease - #75

Merged
danoszz merged 1 commit into
mainfrom
ci/rc-on-next
Oct 20, 2026
Merged

danoszz merged 1 commit into
mainfrom
ci/rc-on-next

Conversation

@danoszz

@danoszz danoszz commented Oct 20, 2026

Copy link
Copy Markdown
Owner

Before the first release candidate: publish.yml staged every tag with npm's default dist-tag, so v1.8.0-rc.1 would have targeted latest (npm 11 also refuses a prerelease without --tag).

  • Tags containing - stage with --tag next; others with --tag latest (unchanged behaviour). npm stage publish --help on the pinned npm 11.21.1 lists --tag.
  • The GitHub release for a prerelease tag is created with --prerelease.
  • CONTRIBUTING step 5 updated; the open to-do note is removed.

No tag, no version bump.

🤖 Generated with Claude Code

A v1.8.0-rc.N tag now stages with --tag next instead of the default latest,
and its GitHub release is marked as a prerelease. Final vX.Y.Z tags are
unchanged. CONTRIBUTING's release steps say so.

AI-Assisted: Claude Code with Claude Opus 5.5; found the missing dist-tag and wrote the workflow change
Co-Authored-By: Claude Opus 5.5 <[email protected]>
@danoszz
danoszz merged commit 4c755e5 into main Oct 20, 2026
17 checks passed
@danoszz danoszz mentioned this pull request Oct 20, 2026
@danoszz
danoszz deleted the ci/rc-on-next branch October 20, 2026 17:08
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