chore: set bootstrap-sha to trigger initial release-please - #3
Merged
Conversation
Sets the bootstrap-sha to the migration merge commit so release-please knows where to start scanning for conventional commits. 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
Sets the
bootstrap-shainrelease-please-config.jsonto the migration merge commit (1cfbf42). This tells release-please where to start scanning for conventional commits, which will trigger the initial release PR.What this does
REPLACE_WITH_FIRST_COMMIT_SHA_AFTER_MIGRATIONplaceholder with the actual SHA of the merge commit from feat: initial commit — LaunchDarkly AI SDK for Python #1mainwith afeat:orfix:commit will generate a release-please PR bumping all packages from0.0.0to their first version