Skip to content

chore(changeset): promote to v1.0.0 stable#220

Open
s-adamantine wants to merge 3 commits into
mainfrom
release/v1.0.0-stable-promotion
Open

chore(changeset): promote to v1.0.0 stable#220
s-adamantine wants to merge 3 commits into
mainfrom
release/v1.0.0-stable-promotion

Conversation

@s-adamantine
Copy link
Copy Markdown
Contributor

@s-adamantine s-adamantine commented Jun 3, 2026

What

Adds a single major changeset file (.changeset/promote-to-v1-stable.md) so the next changesets Release PR bumps the package from 0.13.01.0.0.

That's the entire diff of this PR vs main:

$ git diff origin/main...HEAD --stat
 .changeset/promote-to-v1-stable.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

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.yml consumes the pending .changeset/*.md files, it will combine every unconsumed changeset on main at that moment into one release. As of now that means:

Changeset Bump Source Effect on 1.0.0
promote-to-v1-stable.md major this PR forces 0.13.01.0.0
increase-workscope-string-limit.md minor already on main via #212 raises org.hypercerts.claim.activity work scope string from 100 → 1,000 graphemes (10,000-byte cap)

The major bump wins for version determination, so the final version is 1.0.0 (not 0.14.0 from the minor). Both changeset bodies will appear under the ## 1.0.0 heading in CHANGELOG.md.

If any further changesets land on main before the release workflow is run, they'll also be folded into 1.0.0 automatically.

Verification

$ npx changeset status --verbose
🦋  info Packages to be bumped at major
🦋  - @hypercerts-org/lexicon 1.0.0
🦋    - .changeset/increase-workscope-string-limit.md
🦋    - .changeset/promote-to-v1-stable.md

Local npm run check (lint + typecheck + build + 147 tests) passes.

Release flow from here

  1. Merge this PR
  2. Manually run release.yml on main → opens a "Release v1.0.0" PR (bumps package.json, updates CHANGELOG)
  3. Merge that PR
  4. Manually run release.yml on main again → publishes 1.0.0 to npm + tags v1.0.0

See docs/PUBLISHING.md for the full workflow.

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.
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jun 3, 2026

🦋 Changeset detected

Latest commit: 5987d08

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@hypercerts-org/lexicon Major

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

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 3, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

The PR adds a changeset entry promoting @hypercerts-org/lexicon to stable v1.0.0 release. The changeset declares no schema changes from v0.13.0, confirms TypeScript types and generated exports are stable, and establishes SemVer versioning semantics going forward.

Changes

v1.0.0 Stable Release

Layer / File(s) Summary
v1.0.0 stable release promotion
.changeset/promote-to-v1-stable.md
Changeset entry marks the lexicon package as promoted to stable v1.0.0 major version with backward-compatible schema, confirming types and generated exports are stable for downstream use.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • aspiers

Poem

🐰 From zero-point-thirteen, a journey complete,
The lexicon hops to stability's beat,
v1.0.0 shines with types now assured,
No schemas did change—the contract's secured,
SemVer awaits on this stable new street! 📦✨

🚥 Pre-merge checks | ✅ 7
✅ Passed checks (7 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore(changeset): promote to v1.0.0 stable' directly and clearly describes the main change—promoting the package to v1.0.0 stable release via a changeset file. It is concise, specific, and accurately summarizes the primary objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Lexicon Documentation Sync ✅ Passed All lexicons documented in README and ERD have corresponding JSON files; entities in ERD match lexicon IDs; documentation and lexicons are properly synchronized in initial commit.
Lexicons Styleguide Compliance ✅ Passed PR adds new lexicon files with 0 style errors; 5 warnings are non-blocking best-practice guidance and require no deviations documentation.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v1.0.0-stable-promotion

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Pulls in #212 (increase activity work scope string limit, minor)
so PR #220 stays up-to-date and the eventual v1.0.0 release
correctly combines both pending changesets.
The release that ships v1.0.0 will combine this changeset with the
'increase activity work scope string limit' changeset (added via
#212 / 871608f). Reword this changeset so it describes its own
contribution (force major bump only) rather than implying the
whole v1.0.0 release is schema-clean.
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.

2 participants