chore: remove release-please workflow and configs#23401
Merged
Conversation
AztecBot
changed the title
ludamad
added
backport-to-v4
and removed
claudebox
ludamad
changed the title
## Summary Conservative pass on `next` — keeps `.release-please-manifest.json` (still used as the version source by `bootstrap.sh`, workflows, `ci3/source_refname`, playground, telemetry, pxe, spartan scripts, release-image Docker, etc.) and removes only the release-please tooling and stale doc references. ### Removed - `.github/workflows/release-please.yml` — the googleapis/release-please-action workflow - `.github/release-please-master.json`, `-v2.json`, `-v3.json`, `-v4.json` — release-please configs - The `x-release-please-*` magic-comment blocks in both Docusaurus configs (these were release-please tool markers) ### Doc updates (no functional changes) - `README.md` Releases paragraph — points at tags + manifest instead of release-please - `bootstrap.sh` comment — drop "release-please creates it" aside - `docs/scripts/cli_reference_generation/CLI_DOCS_README.md` — drop dead `release-please.yml` reference - `spartan/testnet-runbook.md` — describe tag-driven release instead of "initiate a release-please workflow" - `.claude/skills/merge-train-infra` — describe `BEGIN/END_COMMIT_OVERRIDE` markers without claiming they're consumed by release-please - `yarn-project/BRANCHING.md` — fix one dead link to `release-please.yml`; the rest of BRANCHING.md (including v2's still-active release-please description and all `.release-please-manifest.json` references) is left alone ### Intentionally NOT touched (per "more conservative" scope) - `.release-please-manifest.json` — kept as the canonical version source - `create-release-branch.yml` — still bumps `.release-please-manifest.json` (manifest stays) - All workflows / bash / TS / JS that read the manifest — all unchanged - `docs/README.md` macro paragraph naming the manifest — still accurate - `.claude/skills/updating-changelog` — still tells you to read the manifest - `.claude/skills/noir-sync-update` — references the noir submodule's own manifest, out of scope - v2's release-please description in `BRANCHING.md` — `v2` still has release-please; only `next` changes - `v4-next` — companion PR #23402 closed; only `next` per request 13 files changed, 6 insertions(+), 436 deletions(-). ## Test plan - [ ] CI green (no consumer touched, no version-resolution path changed) - [ ] release-image build still stamps `.release-please-manifest.json` and `aztec --version` is correct
aminsammara
approved these changes
May 20, 2026
Contributor
|
LGTM! |
Collaborator
Author
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
Collaborator
Author
|
❌ Failed to cherry-pick 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
3 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
Conservative pass on
next— keeps.release-please-manifest.json(still used as the version source bybootstrap.sh, workflows,ci3/source_refname, playground, telemetry, pxe, spartan scripts, release-image Docker, etc.) and removes only the release-please tooling and stale doc references.Removed
.github/workflows/release-please.yml— the googleapis/release-please-action workflow.github/release-please-master.json,-v2.json,-v3.json,-v4.json— release-please configsx-release-please-*magic-comment blocks in both Docusaurus configs (these were release-please tool markers)Doc updates (no functional changes)
README.mdReleases paragraph — points at tags + manifest instead of release-pleasebootstrap.shcomment — drop "release-please creates it" asidedocs/scripts/cli_reference_generation/CLI_DOCS_README.md— drop deadrelease-please.ymlreferencespartan/testnet-runbook.md— describe tag-driven release instead of "initiate a release-please workflow".claude/skills/merge-train-infra— describeBEGIN/END_COMMIT_OVERRIDEmarkers without claiming they're consumed by release-pleaseyarn-project/BRANCHING.md— fix one dead link torelease-please.yml; the rest of BRANCHING.md (including v2's still-active release-please description and all.release-please-manifest.jsonreferences) is left aloneIntentionally NOT touched (per "more conservative" scope)
.release-please-manifest.json— kept as the canonical version sourcecreate-release-branch.yml— still bumps.release-please-manifest.json(manifest stays)docs/README.mdmacro paragraph naming the manifest — still accurate.claude/skills/updating-changelog— still tells you to read the manifest.claude/skills/noir-sync-update— references the noir submodule's own manifest, out of scopeBRANCHING.md—v2still has release-please; onlynextchangesv4-next— companion PR chore: remove release-please (v4-next) #23402 closed; onlynextper request13 files changed, 6 insertions(+), 436 deletions(-).
Test plan
.release-please-manifest.jsonandaztec --versionis correct