Changes
Release preparation, notes, and publication now follow one reviewed process.
Upgrade
- Maintainers: replace
release-tag vX.Y.Zwith
scripts/release/release-tag prepare vX.Y.Z. Review and commit the prepared
files, then runscripts/release/release-tag finalize vX.Y.Z. Preparation no
longer commits or creates a tag. Neither command pushes. - Use
releasing-codefor release notes instead ofdocumenting-code.
Added
releasing-codeowns release preparation, publication, and notes-only repair.
English and Russian release requests now receive the matching skill suggestion.- Optional
release-guardchecks direct GitHub release writes. Enable it with
HOOK_RELEASE_GUARD=1; it remains off by default. Enabled checks require
Python 3.11+. A disabled guard does not require Python. - Notes-only repair accepts a committed correction for an existing stable release,
saves its previous title and body in a 90-day backup, and preserves its assets
and tag. Drafts and prereleases are rejected.
Changed
- Release notes come from the committed changelog. Checks reject placeholder-only
notes and mismatches between the tag and package versions before publication. - GitHub releases use the exact tag as their title. Third-party release actions
are pinned to verified commit SHAs.
Plugins
| Plugin | Description |
|---|---|
| browser | Browser-based testing, validation, screenshots, recordings, and quick automation |
| dev-flow | Code review, fixes, commits, release flows, and linting for development workflows |
| discovery | Research, docs lookup, utility routing, skill authoring, instruction review, reasoning, and agent configuration audits |
| git-flow | Git worktrees, branch cleanup, hooks, secret scanning, config hygiene, and guardrails |
| infra-ops | Kubernetes, Terraform, Helm, GitHub Actions, AWS, GCP, and Linux infrastructure operations |
| programming | Idiomatic development across C# /.NET, Go, Java/Kotlin, Python, Rust, TypeScript, shell, and web |
| spec-flow | Lightweight spec loop: plan one slice, execute one task, checkpoint or close |
Distribution
Artifacts are rendered by Agent Bundler from the repository root:
agbun build --root .