• v0.1.21 dc0efdf849

    v0.1.21 Stable

    pipeline-bot released this 2026-07-08 16:26:34 +00:00 | 177 commits to main since this release

    Changed

    • Follow the pipelines land → merge verb rename: the autoland sensor now submits pipeline-merge
      (was pipeline-land) with <proj>-merge-auto- workflow names + <proj>-merge purpose, and the
      PipelineBuild.status.trigger enum is push;merge;manual (was land). The autoland feature
      name (spec.deploy.flux.autoland, the <proj>-autoland sensor) is unchanged.

    Added

    • PipelineRelease.status.deployable + a /active query endpoint — "Releases are Deployable", and
      the dashboard pulse becomes CR-sourced.
      Deployable mirrors PipelineBuild.status.releasable: a
      sticky bool the WorkflowProjector latches true once the release run Succeeds (tag/artifacts
      published), never cleared by a later Failed/Running re-projection. Adds a Deployable printcolumn +
      ReleaseLeg.deployable in the query API. New GET /active returns every project with a
      Running/Pending Change CR (one per line, text/plain, matching the old active.txt wire format) so
      the dashboard sidebar pulse can read the SAME Change CRs the panes do — making pulse ⟺ a visible Running/Pending row true by construction. Envtest asserts the sticky latch; a query unit test
      asserts active(p) ⟺ ∃ non-terminal row in panes(p).

    Included changes (v0.1.20 -> v0.1.21)

    • 8c7f7bd72cd8 refactor(pipeline): follow land->merge verb rename
    • e79c4105e66b ci: re-trigger (buildkitd restarted for rotated token)
    • 6c8e4e5ea6fa ci: re-trigger (pipeline-bot token rotated post-migration)
    • 0e58f1474571 ci: re-trigger (forgejo back up)
    • 2065b983f444 ci: re-trigger (forgejo git-fetch recovered post-migration)
    • 803174126630 ci: re-trigger (compile leg hit a forgejo git-fetch 403)
    • 352e03d350d6 feat(cd-state): PipelineRelease.Deployable + /active endpoint (pulse ⟺ running)
    Downloads