-
Notifications
You must be signed in to change notification settings - Fork 1
fix(storage): release rule #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Greptile OverviewGreptile SummaryFixes monorepo release isolation by preventing commits scoped to one package from triggering releases in other packages. Previously, a
Confidence Score: 4/5
Important Files Changed
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No files reviewed, no comments
f987faf to
31e13da
Compare
31e13da to
b03ba16
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No files reviewed, no comments
|
🎉 This PR is included in version 1.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.12.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Note
Refines release process to avoid cross-package releases and ensures CI dry-run tests the correct branch.
release.config.base.cjsto apply semantic-release rules only to the package scope and block releases from other scopes using negation rules.github/workflows/pr.yamlto checkoutgithub.head_refand runrelease:dry-runwithGITHUB_TOKENscripts/release.shdry-run to use current/PR branch, skip npm verification, verify only GitHub conditions, and unsetGITHUB_ACTIONSWritten by Cursor Bugbot for commit b03ba16. This will update automatically on new commits. Configure here.