-
v0.1.34 Stable
released this
2026-07-14 23:21:42 +00:00 | 112 commits to main since this releaseFixed
- Zombie reaper now reaps a release wedged in its prepare stage. The reaper checked only
Status.Workflow, which is empty during the release prepare stage (onlyStatus.PrepareWorkflow
is set then;Status.RunWorkflowis the run stage).workflowGone("")is false, so a release whose
prepare workflow vanished — TTL-GC, cancel-stale supersession, or a delete missed while the operator
was down — was never reaped and wedgedPendingforever (a perpetual dashboard row, a stuck ship
intent). The reaper now evaluates all three refs viareleaseWorkflowsGoneand reaps only when at
least one ref exists and every non-empty ref is gone — so a run-stage release whose prepare workflow
was normally GC'd but whose run workflow is still live is spared. - Status anti-downgrade no longer bypassed by a start-less event.
projectSingle's guard only
fired when both the stored and incomingStartedAtwere non-nil, so a stalePendingre-delivery
(which has no start time) overwrote aSucceededrun and nil'd the stored start — permanently
disabling the guard and flapping the status. A nil incomingStartedAtnow counts as the oldest
possible activity and can never downgrade a run that already started. - Pin resolver no longer latches a blank commit SHA on a transient Forgejo miss.
TagSHAreturns
""on any transient failure (network, non-200, restart); the resolver minted aPipelineDeploywith
a blankSpec.SHA, and the idempotent(artifact, version)guard then skipped every later sweep —
latching the blank traceability sha forever. A blank sha now defers minting to a later sweep, which
resolves the real sha once Forgejo recovers.
Included changes (v0.1.33 -> v0.1.34)
c49b95dca9b0fix(projector): reap prepare-stage zombies, close anti-downgrade nil-gap, defer blank-sha pins
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- Zombie reaper now reaps a release wedged in its prepare stage. The reaper checked only