chore: sync release-please manifest with account-sdk 2.5.4#277
Merged
Conversation
The manifest was pointing to 2.5.3 while package.json and the GitHub release are already at 2.5.4. This mismatch caused release-please to look for commits from the wrong base, preventing it from creating a release PR for account-sdk. Made-with: Cursor
Collaborator
✅ Heimdall Review Status
|
fan-zhang-sv
changed the title
montycheese
approved these changes
Apr 16, 2026
stephancill
approved these changes
Apr 16, 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
4 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
.release-please-manifest.jsonto point account-sdk at2.5.4(matching the actualpackage.jsonversion and GitHub release)2.5.3, causing release-please to scan from the wrong base commit and skip account-sdk when generating release PRsTest plan
Made with Cursor