Release
v2.1.0
tidy upArgus now prunes the stale branches it leaves behind and runs its cleanup consistently across Maven and npm.
Highlights
- 01
Stale branch pruning
Opt-in ARGUS_PRUNE_BRANCHES deletes Argus-owned branches that have no open merge request after a successful reconciled run, so repositories stop accumulating dead argus/ branches once their MRs are closed or merged.
Read the guide → - 02
Cleanup parity across ecosystems
MR reconciliation and branch pruning now run for npm as well as Maven, matching the stale-override cleanup that already covered both. npm and Maven projects are tidied identically after a run.
Full notes
Added
- Opt-in stale branch pruning (ARGUS_PRUNE_BRANCHES, default off): after a successful reconciled run, Argus-owned branches with no open MR whose tip commit was authored by Argus are deleted. Default, protected, desired, and human-edited branches are never touched (ADR-029).
- CI/CD component prune_branches input (default off), mapped to ARGUS_PRUNE_BRANCHES, so component users can enable branch pruning.
Changed
- MR reconciliation and branch pruning are extended to the npm pipeline, so cleanup is consistent across Maven and npm.