chore(changeset): promote to v1.0.0 stable#220
Conversation
Adds a major changeset so the next changesets Release PR bumps 0.13.0 → 1.0.0. The release contains no schema changes from v0.13.0; the bump signals that the lexicons, types, and generated exports are now considered stable and switches the package onto standard SemVer semantics.
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.
Tip: disable this comment in your organization's Code Review settings.
🦋 Changeset detectedLatest commit: 5987d08 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📝 WalkthroughWalkthroughThe PR adds a changeset entry promoting Changesv1.0.0 Stable Release
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 7✅ Passed checks (7 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
Adds a single
majorchangeset file (.changeset/promote-to-v1-stable.md) so the next changesets Release PR bumps the package from0.13.0→1.0.0.That's the entire diff of this PR vs
main:No schema edits, no generated-code edits, no API edits. This PR is purely a version-bump signal for changesets.
Why
Marks the lexicons, TypeScript types, and generated exports as stable for downstream consumers and shifts the package onto standard SemVer semantics (future breaking changes → major, non-breaking additions → minor, fixes → patch).
What the eventual v1.0.0 release will contain
The release is not just this changeset. When
release.ymlconsumes the pending.changeset/*.mdfiles, it will combine every unconsumed changeset onmainat that moment into one release. As of now that means:1.0.0promote-to-v1-stable.mdmajor0.13.0→1.0.0increase-workscope-string-limit.mdminormainvia #212org.hypercerts.claim.activitywork scope string from 100 → 1,000 graphemes (10,000-byte cap)The
majorbump wins for version determination, so the final version is1.0.0(not0.14.0from theminor). Both changeset bodies will appear under the## 1.0.0heading inCHANGELOG.md.If any further changesets land on
mainbefore the release workflow is run, they'll also be folded into1.0.0automatically.Verification
Local
npm run check(lint + typecheck + build + 147 tests) passes.Release flow from here
release.ymlonmain→ opens a "Release v1.0.0" PR (bumpspackage.json, updates CHANGELOG)release.ymlonmainagain → publishes1.0.0to npm + tagsv1.0.0See
docs/PUBLISHING.mdfor the full workflow.