sean/pipelines
Watch
1
0
Fork
You've already forked pipelines
 0
Code Issues Pull requests 12 Projects Releases 291 Packages Wiki Activity
291 releases 291 tags
  • v0.1.64 7a4a24a224

    v0.1.64 Stable

    gitea_admin released this 2026-07-05 17:38:53 +00:00 | 1028 commits to main since this release

    Added

    • A Failed release now shows WHERE it died, even when that step's log is credential-gated. A
      release run's promote/sign/devbump steps hold Forgejo push tokens + signing keys, so their
      logs are default-denied from the dashboard's credential-safe allowlist — which left a Failed
      release showing only its green safe-step chips (validate/guard/publish) with nothing marking
      the failure. The fold now renders a red, non-clickable "failed at <step> — credential step, log
      withheld · open in Argo →" marker, driven by the query service's ReleaseLeg.failedStep (from
      PipelineRelease.status.failedStep, projected server-side by pipelines-operator — a step NAME,
      never log bytes). panesRows carries it; the marker is suppressed when the failing step is itself
      a published safe chip (its own red chip already shows it), and a credential-step failure with no
      safe log is now foldable so the marker still surfaces.

    Included changes (v0.1.63 -> v0.1.64)

    • f489f96fbbea feat(dashboard): mark WHERE a Failed release died (credential-gated step)
    • c0bff075a858 feat(builder-images): PipelineProject with fast parallel fleet builds (dockerfile-set)
    Downloads