chore: add bootstrap-sha to release-please config#393
Conversation
Release history recon
WalkthroughA bootstrap SHA configuration value is added to the Release Please configuration file. This explicitly references a bootstrap hash for use by the release tooling during version management operations. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #393 +/- ##
=======================================
Coverage 85.82% 85.82%
=======================================
Files 26 26
Lines 1270 1270
Branches 250 250
=======================================
Hits 1090 1090
Misses 110 110
Partials 70 70 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Updates the repository’s release-please configuration to set a bootstrap commit SHA, enabling release-please to reconstruct/anchor release history from a specific point in git history.
Changes:
- Add
bootstrap-shatorelease-please-config.jsonto define the commit from which release-please should bootstrap release history.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Release history recon
Description
This is a temporary bootstrap to make release please avoid walking through the entire history of the commits because the last time it did so and also couldn't reliably find a PR from the target branch to main ( the rules were modified, as it was originally meant to be just the top package level but when we did the last release we did some manual stuff to sync the release and main branches as the last release tag was pushed from the release branch)
We will revert this after a successful automation release on the right source and target branches.
This also makes the releases draft by default, so we can modify stuff and ensure everything is good and only then publish it.
What problem is being solved?
How is it being solved?
What changes are made to solve it?
References
Review Checklist
mainSummary by CodeRabbit