sean/pipelines
Watch
1
0
Fork
You've already forked pipelines
 0
Code Issues Pull requests 12 Projects Releases 286 Packages Wiki Activity
286 releases 286 tags
  • v0.1.44 a91b596555

    v0.1.44 Stable

    gitea_admin released this 2026-07-05 10:52:50 +00:00 | 1124 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