fix: push barretenberg source as orphan commit to bb repo on release#21867
Closed
AztecBot wants to merge 6 commits into
Closed
fix: push barretenberg source as orphan commit to bb repo on release#21867AztecBot wants to merge 6 commits into
AztecBot wants to merge 6 commits into
Conversation
…21862) ## Summary Adds a GitHub Actions workflow that copies barretenberg release artifacts from `AztecProtocol/barretenberg` to `AztecProtocol/aztec-packages` releases. This fulfils the promise from the PR #21775 discussion: - When someone creates/publishes a release on aztec-packages (via the GitHub UI), this workflow automatically copies all bb artifacts from the barretenberg repo release for that tag - Can also be triggered manually via `workflow_dispatch` for any tag — anyone on the aztec eng team can run it - This ensures bbup's fallback to aztec-packages works for important releases (e.g. those used by Noir) **Note:** File is in `.github-new/` because CI file changes require ci-allow — move to `.github/workflows/` before merging. ## Test plan - [ ] Move `copy-bb-release-artifacts.yml` from `.github-new/workflows/` to `.github/workflows/` - [ ] Merge into PR #21775 - [ ] After merge, test by creating a draft release on aztec-packages for an existing bb tag and verifying artifacts are copied ClaudeBox log: https://claudebox.work/s/1d50ce33634fed3b?run=1 --------- Co-authored-by: ludamad <adam.domurad@gmail.com>
Also fix dangling reference to renamed release_github function.
AztecBot
added
ci-draft
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.
Summary
Adds the missing piece to PR #21775: on each release, push the
barretenberg/folder contents as a disconnected orphan commit toAztecProtocol/barretenberg, tagged with the release version. This ensures the barretenberg repo has the actual source code at each release tag, not just the GitHub release metadata and binary artifacts.Also fixes a dangling reference to the renamed
release_githubfunction in the private fork release path.Changes
release_bb_github: before creating the GH release, copybarretenberg/into a temp dir,git init, commit as orphan, tag, and push to the bb reporelease_github→release_bb_githubcall in the private fork release path (line ~825)How it works
Each release tag in
AztecProtocol/barretenbergis a single orphan commit containing only the barretenberg source — completely disconnected from any branch. The GitHub release is then created pointing at this tag.ClaudeBox log: https://claudebox.work/s/1a522ce4c151568a?run=2