-
v0.1.21 Stable
released this
2026-07-08 16:26:34 +00:00 | 177 commits to main since this releaseChanged
- Follow the pipelines
land → mergeverb rename: the autoland sensor now submitspipeline-merge
(waspipeline-land) with<proj>-merge-auto-workflow names +<proj>-mergepurpose, and the
PipelineBuild.status.triggerenum ispush;merge;manual(wasland). Theautolandfeature
name (spec.deploy.flux.autoland, the<proj>-autolandsensor) is unchanged.
Added
PipelineRelease.status.deployable+ a/activequery endpoint — "Releases are Deployable", and
the dashboard pulse becomes CR-sourced.DeployablemirrorsPipelineBuild.status.releasable: a
sticky bool theWorkflowProjectorlatches true once the release run Succeeds (tag/artifacts
published), never cleared by a later Failed/Running re-projection. Adds aDeployableprintcolumn +
ReleaseLeg.deployablein the query API. NewGET /activereturns every project with a
Running/Pending Change CR (one per line,text/plain, matching the oldactive.txtwire format) so
the dashboard sidebar pulse can read the SAME Change CRs the panes do — makingpulse ⟺ a visible Running/Pending rowtrue by construction. Envtest asserts the sticky latch; a query unit test
assertsactive(p) ⟺ ∃ non-terminal row in panes(p).
Included changes (v0.1.20 -> v0.1.21)
8c7f7bd72cd8refactor(pipeline): follow land->merge verb renamee79c4105e66bci: re-trigger (buildkitd restarted for rotated token)6c8e4e5ea6faci: re-trigger (pipeline-bot token rotated post-migration)0e58f1474571ci: re-trigger (forgejo back up)2065b983f444ci: re-trigger (forgejo git-fetch recovered post-migration)803174126630ci: re-trigger (compile leg hit a forgejo git-fetch 403)352e03d350d6feat(cd-state): PipelineRelease.Deployable + /active endpoint (pulse ⟺ running)
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Follow the pipelines