gitea_admin
released this
2026-07-04 20:18:39 +00:00
| 1201 commits to main since this release
Added
- "Which changes did this deploy include" (end-to-end traceability, Phase A). The deploy
templates now emit provenance as Argo output params for the pipelines-operator to project onto
PipelineDeploy.status:
pipeline-deploy (gitops-deploy) and pipeline-deploy-flux (gitops-flux) write fromSha
(the previously-deployed tip — pipeline-deploy takes it from the push's body.before via a
new sensor param; the flux twin captures the pre-ff main tip in-workflow), version (the
release tag pointing at the deployed sha, resolved via the Forgejo tags API), and outcome
(deployed/superseded/failed/rolled-back, written at each exit).
- Dashboard: a deploy row now folds open to the commits it shipped — a Forgejo compare
(fromSha...sha) rendered as "N changes since <short>" with per-commit links + a full-compare
link. A deploy row also shows a version chip when the deployed commit is a tagged release, and
the Deploy card reflects outcome (a superseded deploy reads "superseded", not a bare
"Succeeded"). Release rows carry the new requestedBy/image data. All additive: the panes'
uniform identity (build/deploy lead with a 12-char sha, release with vX.Y.Z) is unchanged.
Fixed
- devbump + release-cadence reap their branches on merge.
pipeline-devbump and
pipeline-release-cadence now pass delete_branch_after_merge: true on the PR merge, so
_devbump/*-dev and release-cadence/* branches no longer pile up on Forgejo after every
dev-cycle open / release (matching pipeline-land's feature-branch reap; the promotes already
explicit-DELETE their _promote/*/_devbump/v* temps). The ffpr main-advance merges are
deliberately left untouched — their head is trunk, which must never be deleted.
Downloads