sean/pipelines
Watch
1
0
Fork
You've already forked pipelines
 0
Code Issues Pull requests 12 Projects Releases 282 Packages Wiki Activity
282 releases 282 tags
  • v0.1.52 470ab6bb5c

    v0.1.52 Stable

    gitea_admin released this 2026-07-05 12:41:12 +00:00 | 1062 commits to main 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 | 1068 commits to main 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 | 1073 commits to main 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 | 1080 commits to main 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
  • v0.1.48 ac473ef035

    v0.1.48 Stable

    gitea_admin released this 2026-07-05 11:33:51 +00:00 | 1086 commits to main since this release

    Changed

    • Incremental release.

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

    • 10eb094873f5 fix(kernel): tolerate Forgejo full-sha 404 on API-created merge commits
    Downloads
  • v0.1.47 da41ad5b98

    v0.1.47 Stable

    gitea_admin released this 2026-07-05 11:23:43 +00:00 | 1091 commits to main since this release

    Fixed

    • BUILDS / RELEASES / DEPLOYS tables now column-align. They are three separate <table>s;
      auto-layout sized each one's identity column to its own content (12-char sha vs v0.1.8 vs
      commit+version+target badges), so STATUS/STEPS/DURATION/WHEN landed at a different x in each.
      table.wf is now table-layout:fixed with shared column widths, so all three line up.

    Included changes (v0.1.46 -> v0.1.47)

    • dab7780f23c1 feat(dashboard): publish kernel bake/verify/manifest logs on release rows
    Downloads
  • v0.1.46 696610b9b2

    v0.1.46 Stable

    gitea_admin released this 2026-07-05 11:21:11 +00:00 | 1096 commits to main since this release

    Changed

    • Incremental release.

    Included changes (v0.1.45 -> v0.1.46)

    • 4fe316b9e135 fix(dashboard): column-align the BUILDS/RELEASES/DEPLOYS tables
    • 64641ac7dd7b fix(kernel): poll loops stream+condition-check until terminal
    Downloads
  • v0.1.45 3f335ed113

    v0.1.45 Stable

    gitea_admin released this 2026-07-05 11:05:44 +00:00 | 1103 commits to main since this release

    Fixed

    • Plumbing filter also hides chore: devbump … commits (the second devbump subject format in
      the wild) from the release fold's changes list and the generated "Included changes" notes — it
      leaked into v0.1.44's notes alongside the real Changes. SPA isPlumbing + both promote templates'
      jq filter, kept in sync.

    Included changes (v0.1.44 -> v0.1.45)

    • 9eb76428259e fix(release-notes): plumbing filter also hides 'chore: devbump' commits
    Downloads
  • v0.1.44 a91b596555

    v0.1.44 Stable

    gitea_admin released this 2026-07-05 10:52:50 +00:00 | 1108 commits to main since this release

    Changed

    • Deploy folds now show the RELEASE(S) delivered, not raw commits — cementing the mental model
      in the interface.       "Changes are Releasable, Releases are Deployable": the commit list belongs to
      the RELEASE fold (where it already renders, plumbing-filtered); a deploy fold now says
      "delivers release: v0.1.41" (or the whole gap when a deploy skipped versions, with an explicit
      truncation marker past the fetched release window), plus the existing carrier line. The claim is
      EARNED: a rolled-back deploy says "reverted, not delivered", a failed one "was not delivered",
      a superseded or in-flight one claims nothing (adversarial-review finding — the naive guard let a
      rolled-back deploy assert delivery). The deploy-side Forgejo-compare commit list is removed
      (revisit later if a deploy-side commit view proves necessary).
    • Section headers renamed: BUILD/RELEASE/DEPLOY PIPELINES → BUILDS / RELEASES / DEPLOYS.
    • "Latest" cards collapsed to one-line strips — the tables are newest-first, so the big
      label/value cards only duplicated the top row; each pane now has a single compact
      latest · <id> · <status> · <when> line (release keeps its version+commit links; deploy keeps
      the version chip + → target).

    Included changes (v0.1.43 -> v0.1.44)

    • 6e3a80e32409 fix(dashboard): the 'delivers' claim is earned — review findings
    • 17c96230f2d5 feat(dashboard): deploy folds deliver RELEASES not commits + BUILDS/RELEASES/DEPLOYS headers + one-line latest strips
    • 19eae8fb2373 chore: devbump 0.1.43 -> 0.1.44-dev
    Downloads
  • v0.1.43 8fd3726985

    v0.1.43 Stable

    gitea_admin released this 2026-07-05 10:38:36 +00:00 | 1115 commits to main since this release

    Changed

    • Incremental release.

    Included changes (v0.1.42 -> v0.1.43)

    • 192a526fccfd fix(kernel): serialize kernel bakes + stream the Tekton build log
    • 8df6d2e5d8e3 chore: devbump 0.1.42 -> 0.1.43-dev
    Downloads