Skip to content

Release 0.1.0 - #186

Merged
dave-hillier merged 1 commit into
mainfrom
release-0.1.0
Oct 3, 2026
Merged

dave-hillier merged 1 commit into
mainfrom
release-0.1.0

Conversation

@dave-hillier

Copy link
Copy Markdown
Owner

Releases 0.1.0 instead of 0.1.0-alpha.2. Under semver a 0.x version already says the API can change, so the alpha suffix was redundant.

  • package.json version is 0.1.0, and publishConfig.tag is removed, so this publishes to latest instead of next. latest currently points at 0.1.0-alpha.0.
  • The CHANGELOG Unreleased heading becomes 0.1.0.
  • The README and getting-started page no longer tell people to install @next.
  • release.yml now:
    • fails before publishing if the tag doesn't match the package.json version, or if CHANGELOG.md has no section for that version
    • creates the GitHub release after npm publish, using that changelog section as the notes. Versions with a hyphen (for example 1.0.0-rc.1) are marked as prereleases.
    • needs contents: write to do that

After merging, tag main to publish:

git checkout main && git pull
git tag v0.1.0 && git push origin v0.1.0

🤖 Generated with Claude Code

Drop the alpha suffix and the next dist-tag: 0.x already signals an
unstable API, so 0.1.0 publishes to latest. The release workflow now
checks the tag against package.json, takes the notes from the matching
CHANGELOG.md section before publishing, and creates the GitHub release
after.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@dave-hillier
dave-hillier merged commit 6221001 into main Oct 3, 2026
3 checks passed
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