chore: hotfix release all packages#3387
Conversation
Hotfixes pushed straight to main only bumped the changed packages because --force-publish is ignored when combined with --conventional-commits and --conventional-graduate. Add a release:hotfix script (force-publish, no graduate) and route main pushes whose head commit message contains [hotfix] to it, so all packages are versioned and published together. Co-authored-by: Cursor <cursoragent@cursor.com>
When a hotfix lands on main (head commit contains [hotfix]), cherry-pick it onto a branch from dev and open a PR, so the fix is not lost on the next dev -> main release. On cherry-pick conflict the job fails, signaling a manual backport. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (3)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
|

0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (15.60% Estimated after merge)
What's the purpose of this pull request?
How it works?
How to test it?
Starters Deploy Preview
References
Checklist
You may erase this after checking them all 😉
PR Title and Commit Messages
feat,fix,chore,docs,style,refactor,ciandtestPR Description
breaking change,bug,contributing,performance,documentation..Dependencies
pnpm-lock.yamlfile when there were changes to the packagesDocumentation
@Mariana-Caetanoto review and update (Or submit a doc request)