chore(labs-patches): upstream several patches as one aztec-node PR - #25348
Open
ludamad wants to merge 11 commits into
Open
chore(labs-patches): upstream several patches as one aztec-node PR#25348ludamad wants to merge 11 commits into
ludamad wants to merge 11 commits into
Conversation
One aztec-node PR per patch is not the rule: patches that belong together — typically those that do not depend on a foundation version bump — go up as one PR. `labs-patches/bootstrap.sh upstream` now takes any number of patches and applies them in series order onto one branch (`--branch` to name it); the README and CLAUDE.md say so.
ludamad
force-pushed
the
ad/upstream-batches
branch
from
August 28, 2026 21:14
aa82fb5 to
586d13c
Compare
…eam is a local preview The .patch files are the handoff: the labs team drains them with git am from their own checkout. upstream keeps building the preview branch (the named patches in series order on the recorded base) but no longer prints push or PR commands, and the docs stop describing a foundation-opened aztec-node PR.
ludamad
changed the title
added 4 commits
August 31, 2026 12:01
ludamad
changed the title
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
1 participant
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.
upstreamnow takes any number of patches (numbers or.patchpaths) and prepares one branch inlabs/'s repository with them applied in series order on the recorded base, under your own identity — one aztec-node PR for the patches that belong together, instead of one PR per patch.--branch <name>overrides the default branch name.It pushes nothing; the printed push and
gh pr createcommands need aztec-node write access, so a labs employee runs that step. When the PR lands, the nextbumppast it drops those patches from the series.