chore: flush backport-later PRs to v4-next#21341
Closed
Conversation
This was referenced Mar 11, 2026
The cherry-pick of #21244 only resolved the conflict region (first oracle name), but missed renaming utilityGetBlockHashMembershipWitness to aztec_utl_getBlockHashMembershipWitness.
The hash from next (34238ab5...) doesn't match v4-next's oracle interface. Updated to the correct hash (c4c91e3c...) computed by CI.
AztecBot
force-pushed
the
backport-later-to-v4-next
branch
from
6ff6d28 to
8c888fd
Compare
Contributor
Contributor
|
Closing this as I will backport the PRs here to |
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
Cherry-picks the two PRs that had the
backport-laterlabel intov4-next:oracle_version.ts— took incoming hash)get_membership_witness.nr— removed duplicate struct, updated oracle names toaztec_utl_*)Both conflicts were resolved conservatively by accepting the incoming PR changes.
The
backport-laterlabels on both PRs will be replaced withbackport-to-v4-nextonce this is merged.