Skip to content

chore(labs-patches): upstream several patches as one aztec-node PR - #25348

Open
ludamad wants to merge 6 commits into
ad/foundry-lock-labsfrom
ad/upstream-batches
Open

ludamad wants to merge 6 commits into
ad/foundry-lock-labsfrom
ad/upstream-batches

Conversation

@ludamad

@ludamad ludamad commented Aug 28, 2026

Copy link
Copy Markdown
Collaborator

upstream now takes any number of patches (numbers or .patch paths) and prepares one branch in labs/'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 create commands need aztec-node write access, so a labs employee runs that step. When the PR lands, the next bump past it drops those patches from the series.

@ludamad
ludamad changed the base branch from next to ad/foundry-lock-labs August 28, 2026 20:43
@ludamad
ludamad force-pushed the ad/upstream-batches branch from aa82fb5 to 586d13c Compare August 28, 2026 21:14
@ludamad ludamad changed the title chore(labs-patches): upstream several patches as one aztec-node PR chore(labs-patches): the labs team drains patches; upstream becomes a local preview Aug 31, 2026
@ludamad ludamad changed the title chore(labs-patches): the labs team drains patches; upstream becomes a local preview chore(labs-patches): upstream several patches as one aztec-node PR Aug 31, 2026
@ludamad
ludamad changed the base branch from ad/foundry-lock-labs to next September 1, 2026 00:36
@ludamad
ludamad requested a review from charlielye as a code owner September 1, 2026 00:36
@ludamad
ludamad changed the base branch from next to ad/foundry-lock-labs September 1, 2026 00:43
Adam Domurad added 6 commits September 2, 2026 09:23
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.
…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.
…e; upstream is a local preview"

This reverts commit e68f73a.
@ludamad
ludamad force-pushed the ad/upstream-batches branch from db224b7 to f8ee211 Compare September 2, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant