ci: Fix latest trunk tag for release-please manifest#3006
Merged
Conversation
cqc-alec
approved these changes
Apr 1, 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.
We had to recreate the
hugr-py 0.15.5release with an out-of-trunk commit due to an error in the workflow files .That means the tag is not an ancestor of
mainanymore, sorelease-pleasegets confused when picking the new commits.This PR changes the manifest to the latest in-trunk tag (0.15.4), so things should work fine now.
We'll need to clean the changelog a bit to remove the lines already present in the
0.15.5changelog.drive-by: Bring in the workflow fixes from the
hugr-py-v0.15.5branch.