Repository navigation
[Phase 5] L-9 · Release workflow and first tagged release ⚠️ BREAKING #12
Description
Adapt the AIND release-bump-version-uv.yml to run on merge to main. It computes the version bump from conventional-commit prefixes, runs uv version + uv lock, commits ci: version bump [skip actions], and pushes the tag — so it needs a repo-token secret with push rights to a protected branch (coordinate with X-2).
Cut v0.2.0 with autogenerated GitHub Release notes. GitHub Releases only, no PyPI — the sole consumer is the capsule Dockerfile.
Size: M · Depends on: L-2, X-2 · Blocks: aind-motion-energy-capsule C-2
Activity
chore: bump version to 0.2.0 (L-9) (#31)
chore: promote dev to main (v0.2.0 release, L-9) (#33)
docs: record L-9 manual-release deviation in compliance plan (#34)
1mattbecker commentedon Sep 11, 2026
Done, via a manual release instead of the plan's
release-bump-version-uv.ymlautomation.Deviation: that workflow needs a
repo-tokensecret with push rights to protectedmain, andsvc-aindscicomp(the service account the AIND template expects) is not a collaborator here — real cross-team coordination, not a config tweak. For a solo-maintainer repo doing infrequent releases, a manual release satisfies L-9's actual requirement (semver + GitHub Releases + changelog) without that secret/service-account surface. Recorded indocs/standards-compliance.md(#34).What happened:
uv version 0.2.0+uv lock,CITATION.cffupdated to match. Merged todev.dev→mainpromotion. (Head branch had to be a merge ofmainintodevrather thandevdirectly — chore: promote dev to main (Phases 0-4, AIND compliance) #28's earlier squash-merge severed shared history for files touched on both branches, producing a falseCITATION.cffadd/add conflict on a plaindev→maindiff.devitself was never touched.)v0.2.0and cut the GitHub Release directly againstmain:git tag v0.2.0 && git push origin v0.2.0gh release create v0.2.0 --generate-notesv0.2.0: tag · releaseVerified:
pyproject.toml,uv.lock,CITATION.cffall agree on 0.2.0;ruff check/format --check,mypy --strict, andpytest(100% coverage gate) all green on the released commit. No behavioral changes — version metadata and release plumbing only.C-2 (aind-motion-energy-capsule) is now unblocked — the tag it pins to exists.