sean/pipelines
Watch
1
0
Fork
You've already forked pipelines
 0
Code Issues Pull requests Projects Releases 758 Packages Wiki Activity
758 releases 759 tags
  • v0.1.58 beba81ff18

    v0.1.58 Stable

    gitea_admin released this 2026-07-05 15:23:53 +00:00 | 2567 commits to trunk since this release

    Added

    • Dashboard panes size themselves to the window. BUILDS / RELEASES / DEPLOYS now render
      as many rows as the viewport can show without page scroll (rowBudget, was a fixed 12-row
      slice that overflowed a laptop and starved a tall monitor). Folding a section frees its row
      budget for the open panes — fold RELEASES + DEPLOYS and BUILDS alone fills the screen, which
      also makes a single-pane 80x24 IBM 5250 render show a useful build history. Repaints on
      resize (debounced) and on section fold/unfold; the release-history fetch limit follows the
      new 25-row cap.
    • Hover a SHA in a release fold to light up exactly its build row. The hover-level
      companion of the open-fold cross-highlight: each commit link in "changes included in this
      release" carries data-cs, and pointing at one highlights the matching BUILDS row brighter
      than the whole-fold wash.

    Included changes (v0.1.57 -> v0.1.58)

    • 7d02ed265420 feat(dashboard): viewport-fit pane sizing + per-sha hover cross-highlight
    Downloads
  • v0.1.57 edbdd28ce5

    v0.1.57 Stable

    gitea_admin released this 2026-07-05 14:57:19 +00:00 | 2572 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.56 -> v0.1.57)

    • dc07f600fc1b feat(kernel): pipeline-deploy-kernel — NO-SSH fleet roll (agent pods)
    Downloads
  • v0.1.56 6274905cc8

    v0.1.56 Stable

    gitea_admin released this 2026-07-05 14:45:41 +00:00 | 2577 commits to trunk since this release

    Changed

    • BUILDS pane: per-app kustomize renders bundled into one renders.tar.gz. pipeline-validate
      wrote ~13 loose render-*.yaml into /dist, and the dashboard draws one button per build artifact
      — so every build row was a wall of buttons. The renders now go to a scratch dir and are tar'd into
      a single renders.tar.gz; MANIFEST + SHA256SUMS stay loose (smoke gate + integrity), so each row
      shows two buttons instead of a dozen.

    Included changes (v0.1.55 -> v0.1.56)

    • eb26a31e1600 fix(dashboard): bundle per-app kustomize renders into one renders.tar.gz
    Downloads
  • v0.1.55 c319cf6e94

    v0.1.55 Stable

    gitea_admin released this 2026-07-05 14:31:59 +00:00 | 2582 commits to trunk since this release

    Fixed

    • promote ff-merge recovers from the Forgejo ff-race instead of 404-looping. When a Forgejo
      restart mid-promote regresses main after a 200 ff-merge, Forgejo's DB keeps the PR merged=true,
      so a retry reusing the same _promote/v<ver> head 404s forever ("target couldn't be found" — bit
      v0.1.54, 8× 404 on round 2). Each round now uses a fresh _promote/v<ver>-r<round> head — a branch
      the DB has not marked merged, which the regressed main can genuinely fast-forward — and fast-breaks
      on a 404 instead of burning ~140s of backoff on a dead PR. A single mid-flight restart no longer
      aborts the whole release. See forgejo-ffrace-dbcred-restart (the restart sources are being reduced
      in parallel via Forgejo eviction/reloader hardening).

    Included changes (v0.1.54 -> v0.1.55)

    • 425cf6d42786 fix(promote): fresh _promote branch per ff round to survive the Forgejo ff-race
    Downloads
  • v0.1.54 b0ac6de083

    v0.1.54 Stable

    gitea_admin released this 2026-07-05 13:42:31 +00:00 | 2587 commits to trunk since this release

    Added

    • Cross-highlight: opening a release fold lights up its commits in the BUILDS pane. A release's
      change-list commits (the fold) now tint the matching build rows the same blue as the fold's commit
      links, so you can see at a glance which builds a release shipped.
    • Deploy rows show a chip for EACH release delivered. A deploy that skipped a version delivers
      the whole gap — the row now shows every delivered version in purple (e.g. v0.1.50 · v0.1.49),
      matching the fold's "delivers N releases" line instead of showing only the top one (capped at 4 + "+N").

    Included changes (v0.1.53 -> v0.1.54)

    • 93f783568d51 feat(dashboard): cross-highlight release commits in builds + multi-chip delivered releases
    Downloads
  • v0.1.53 074e4d0ffb

    v0.1.53 Stable

    gitea_admin released this 2026-07-05 13:18:47 +00:00 | 2592 commits to trunk since this release

    Fixed

    • RELEASES pane shows a project's real release history, not just CR-backed runs. It was fed only
      by PipelineRelease Change CRs — created when the operator's projector observes a version-cutting
      run — so a project whose release runs aged out (retention / make rebuild wipes CRs) showed
      "(no release runs yet)" even with live releases on Forgejo (e.g. openbao-operator: 0 CRs but
      v0.12.x tags + a live deploy). The pane now merges the durable Forgejo history (RELS, already
      fetched for the folds) as rows for any version lacking a CR run — folding to its artifacts/notes
      like any release row. (Separately worth checking why the projector isn't minting those CRs.)

    Included changes (v0.1.52 -> v0.1.53)

    • 8c09b4543e3b feat(dashboard): link each artifact to its OCI image in zot
    • 9ddadac7e593 feat(dashboard): RELEASES pane surfaces Forgejo release history, not just CR runs
    Downloads
  • v0.1.52 470ab6bb5c

    v0.1.52 Stable

    gitea_admin released this 2026-07-05 12:41:12 +00:00 | 2599 commits to trunk since this release

    Changed

    • Left-nav "moving" indicator now pulses the project LABEL instead of a dot. Same trigger (any
      Running/Pending pipeline, via /api/active), but the label text breathes muted↔accent — the dot
      pseudo-element is gone. (It legitimately lingers as long as real work runs — e.g. an operator's
      post-land trunk build is a ~15-20 min multi-arch image build — so the pulse just reads as "this
      project is doing something.")

    Included changes (v0.1.51 -> v0.1.52)

    • 4086acee8c7c feat(dashboard): nav 'moving' indicator pulses the label text, not a dot
    Downloads
  • v0.1.51 6f69daa2b3

    v0.1.51 Stable

    gitea_admin released this 2026-07-05 12:19:49 +00:00 | 2605 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.50 -> v0.1.51)

    • 64bcec87594c fix(kernel): set explicit command on cosign-one (distroless entrypoint)
    Downloads
  • v0.1.50 438f1d8211

    v0.1.50 Stable

    gitea_admin released this 2026-07-05 12:02:58 +00:00 | 2610 commits to trunk since this release

    Fixed

    • CHANGELOG lands stop conflicting: .gitattributes marks CHANGELOG.md merge=union. Two
      branches landing close together (or one landing right after a release promoted [Unreleased])
      collided on the changelog every time, even though the bullets never overlapped — each land needed
      a manual rebase just to reconcile it. The built-in union merge driver keeps BOTH sides' lines
      instead of raising a conflict (land uses Do:merge, a real 3-way merge, so the driver applies).

    Included changes (v0.1.49 -> v0.1.50)

    • ffc574651696 fix(cicd): auto-resolve CHANGELOG land conflicts via .gitattributes merge=union
    • 1430f9e83d6a fix(kernel): fetch mc static client in promote do-release (alpine/k8s lacks it)
    Downloads
  • v0.1.49 9670e04075

    v0.1.49 Stable

    gitea_admin released this 2026-07-05 11:50:19 +00:00 | 2617 commits to trunk since this release

    Changed

    • Declutter: removed the "Latest" strips and the dead STEPS column. The tables are newest-first,
      so each "Latest · …" line just restated the top row — gone. The STEPS column showed each row's
      progress, which the Change-CR parsers (parsePBuild/parsePRel/parsePDep) always leave empty,
      so it was a permanent void between STATUS and DURATION — dropped (BUILDS/RELEASES/DEPLOYS are now
      commit|version · status · duration · when). Tables cap at a compact width instead of sprawling
      across an ultrawide monitor. (releaseRender/renderLatest* removed; RELS still feeds the
      release/deploy folds via fetchReleases, repainting through wfRender.)

    Included changes (v0.1.48 -> v0.1.49)

    • 23850c643109 feat(dashboard): remove Latest strips + the dead STEPS column
    Downloads