feat(ci): private-nightly docker release series + next-net source - #23788
Open
ludamad wants to merge 3 commits into
Open
feat(ci): private-nightly docker release series + next-net source#23788ludamad wants to merge 3 commits into
ludamad wants to merge 3 commits into
Conversation
added 3 commits
June 1, 2026 23:03
Adds a private nightly series, sourced from the embargoed v5 line in
aztec-packages-private/v5-next, that publishes the aztec docker image only.
- bootstrap.sh: ci-release gains a `*-private-nightly.<date>` path that fetches
the matching tag from the private fork, builds it, and publishes just the
release-image docker image (no npm/cargo/github, no compat gate). The
existing private-fork checkout is factored into checkout_private_worktree and
reused by both private paths.
- nightly-release-tag-private.yml: scheduled tagger that reads
private/v5-next's version, tags v{version}-private-nightly.<date> in the
private repo (build source) and pushes the same tag to public next (the
trigger). Guarded to the public repo so the private mirror can't misfire.
next-net now tracks the private v5 line: the scheduled deploy resolves aztecprotocol/aztec:<priv-version>-private-nightly.<date>-amd64 from private/v5-next instead of the public nightly. Manual image_tag dispatch is unchanged. Kept separate so it can be gated/reverted independently.
- ci3.yml: exclude -private-nightly. from the validate-nightly-tag gate; without this the substring match fired the full ci-network-scenario matrices against the docker-only private nightly every night (BLOCKER from review). - bootstrap.sh: no-op the private-nightly path in the private mirror so a mirrored tag push can't trigger a second, self-fetching ci-release in the embargoed repo. - nightly-release-tag-private.yml: abort in the cheap tagger on a real private tag-create failure (only continue if the tag already exists) instead of pushing a public trigger for a missing source; make the public tag push idempotent; fix a stale deploy-time comment.
ludamad
force-pushed
the
ad/feat/private-nightly-releases
branch
from
June 2, 2026 03:06
d6462e9 to
a740833
Compare
alexghr
approved these changes
Jun 2, 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.
Stacked on #23780 (ci-release unification). Sets up a private nightly release series sourced from the embargoed v5 line, publishing the docker image only, which next-net then deploys.
Pieces
bootstrap.sh—ci-releasegains a*-private-nightly.<date>path (checked before the genericprivate*): fetch the matching tag fromaztec-packages-private, build it, publish only therelease-imagedocker image — no npm/cargo/github, no compat gate. Existing private-fork checkout refactored intocheckout_private_worktree, shared by both private paths..github/workflows/nightly-release-tag-private.yml(new) — scheduled 1 AM UTC: readsprivate/v5-next's version → tagsv{version}-private-nightly.<date>in the private repo (build source) and pushes the same tag to publicnext(the trigger). Guarded to the public repo so the private mirror can't misfire..github/workflows/deploy-next-net.yml— scheduled deploy resolvesaztecprotocol/aztec:<priv-version>-private-nightly.<date>-amd64fromprivate/v5-next(separate commit, easy to gate).Flow
The public trigger tag runs
ci-releasefrom publicnext, so theprivate-nightlypath must already be merged there — otherwise a…-private-nightlytag falls into the genericprivate*path and does a FULL release, not docker-only. So: merge #23780 → merge this → then enable the tagger.Notes
private/v5-nextbranch is created (fromprivate:next, v5.0.0). No private-repo code change is needed — orchestration is public.