Skip to content

fix(repo): seed prerelease versions for beta releases#195

Merged
qantrepreneur merged 1 commit into
mainfrom
194-fix-prerelease-manifest
May 23, 2026
Merged

fix(repo): seed prerelease versions for beta releases#195
qantrepreneur merged 1 commit into
mainfrom
194-fix-prerelease-manifest

Conversation

@qantrepreneur
Copy link
Copy Markdown
Contributor

Summary

  • Seed manifest and package.json versions to 0.0.1-beta.0 so release-please enters prerelease mode
  • Starting from 0.0.0, release-please ignores prerelease config and jumps to 1.0.0
  • With this seed, future releases will produce proper beta versions (e.g. 0.0.1-beta.1)

Closes #194

Test plan

  • Merge this PR and verify that release-please updates PR chore: release main #34 to use beta prerelease versions instead of 1.0.0
  • If PR chore: release main #34 still shows 1.0.0, close it and let a new release-please run create a fresh one

🤖 Generated with Claude Code

…leases

Starting from 0.0.0, release-please jumps to 1.0.0 ignoring prerelease
config. Seeding with 0.0.1-beta.0 puts it in prerelease mode so future
releases produce proper beta versions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@qantrepreneur qantrepreneur merged commit 2f9f33e into main May 23, 2026
3 checks passed
@qantrepreneur qantrepreneur mentioned this pull request May 23, 2026
This was referenced May 23, 2026
@qantrepreneur qantrepreneur deleted the 194-fix-prerelease-manifest branch May 24, 2026 13:03
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.

ci: Better Notify-style npm release channels (canary + beta) and versioned docs

1 participant