fix: set bootstrap-sha to pre-migration commit - #5
Merged
Conversation
The bootstrap-sha was pointing to the migration feat commit itself, causing release-please to skip it. Points to the initial repo commit instead so the migration is included as a releasable change. Co-authored-by: Cursor <cursoragent@cursor.com>
tracisiebel
approved these changes
Jul 31, 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.
Summary
The
bootstrap-shawas set to the migration merge commit itself (1cfbf42), which caused release-please to skip thatfeat:commit since it ignores commits at and before the bootstrap-sha.This updates it to the original repo initialization commit (
7a6f420) so the migrationfeat:commit is included as a releasable change.Merging this PR will also trigger a fresh release-please run that should create the v0.1.0 release PR.