ci: changesets v3 & split release workflow - #8051
Open
Sheraff wants to merge 2 commits into
Open
Conversation
Contributor
|
View your CI Pipeline Execution ↗ for commit 685c4de
☁️ Nx Cloud last updated this comment at |
Contributor
🚀 Changeset Version Preview4 package(s) bumped directly, 19 bumped as dependents. 🟩 Patch bumps
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe Changesets schema and package versions were upgraded. The release workflow now separates mode selection, versioning, packing, npm publication, and GitHub release creation with conditional jobs and scoped permissions. ChangesRelease pipeline modernization
Estimated code review effort: 4 (Complex) | ~45 minutes Merge Risk: ⚪ Minimal · up to This PR updates the release workflow and Changesets configuration; no actionable merge-blocking risk remains based on the supplied evidence. Sequence Diagram(s)sequenceDiagram
participant GitHubActions
participant select-mode
participant version
participant pack
participant publish
participant npm
participant release
participant GitHub
GitHubActions->>select-mode: select release mode and channel
select-mode->>version: provide mode and channel outputs
version->>pack: provide publish-plan artifact
pack->>publish: provide packed-directory artifact
publish->>npm: publish packed packages
publish->>release: report successful publication
release->>GitHub: create GitHub release
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 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 |
| on: | ||
| push: | ||
| branches: [main, '*-pre', '*-maint'] | ||
| # we do not support '*-maint' branches at this time |
Collaborator
There was a problem hiding this comment.
what is the -maint suffix?
Collaborator
Author
There was a problem hiding this comment.
i think it was meant for "maintenance" branches, but i'm not entirely sure
Sheraff
commented
Aug 14, 2026
Sheraff
commented
Aug 14, 2026
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
2 participants
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.
split release workflow = better security
https://e18e.dev/docs/publishing.html#standard-workflow
changesets v3 enables it
https://changesets.dev/guide/migration
Closes #7692 (a previous attempts, w/ pre-release changesets packages)
Summary by CodeRabbit
Release Process
Maintenance