chore(release): adopt Changesets and verified package releases - #127
Merged
Merged
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (42)
✨ 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace Semifold with Changesets so source PRs carry package-scoped release notes, and a generated release PR updates versions, exact internal dependencies, lockfiles, and changelogs together.
The alpha publishing path validates the release commit, preserves existing
latesttags across partial-publication retries, checks exact registry versions, and creates per-package GitHub Releases only after acceptance. Existing unpublished changes from #108, #122, and #125 are carried forward. Beta publication remains separate work under #26.Validation: release contract suite, real Changesets version/consume/repeat/stable-exit rehearsal, official offline packing, registry and GitHub API fixtures, release metadata, documentation checks, changeset policy, and safe dist-tag dry-run passed. No npm publication was performed.
Historical changelogs for all 10 packages were restored separately in #128 and are included here as the audited baseline for the new history-preservation check.
Setup required: the organization currently forbids Actions from creating pull requests. An owner must enable that policy, followed by the repository setting, for automatic version PRs. The maintainer guide includes the same version-and-review process as a manual fallback. A denied PR creation fails the workflow and cannot publish packages.