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.48 ac473ef035

    v0.1.48 Stable

    gitea_admin released this 2026-07-05 11:33:51 +00:00 | 2623 commits to trunk 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 | 2628 commits to trunk 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 | 2633 commits to trunk 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 | 2640 commits to trunk 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 | 2645 commits to trunk 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 | 2652 commits to trunk 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
  • v0.1.42 c3fea2a9c4

    v0.1.42 Stable

    gitea_admin released this 2026-07-05 10:21:45 +00:00 | 2658 commits to trunk since this release

    Changed

    • Incremental release.

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

    • 7cb0a57fb377 feat(kernel): P2 release — pipeline-promote-kernel + mode flip
    • 68d6f4000222 chore: devbump 0.1.41 -> 0.1.42-dev
    Downloads
  • v0.1.41 13254f5ecd

    v0.1.41 Stable

    gitea_admin released this 2026-07-05 10:01:32 +00:00 | 2664 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.40 -> v0.1.41)

    • 2fe773e56222 fix(kernel): crane-export the whole rootfs in verify (member path was brittle)
    Downloads
  • v0.1.40 12b485f03f

    v0.1.40 Stable

    gitea_admin released this 2026-07-05 09:51:31 +00:00 | 2669 commits to trunk since this release

    Added

    • Release contents as DATA — "included changes" on every release, no CHANGELOG discipline
      required.       (Motivating bug: pipelines-operator v0.1.8 shipped two Changes but one landed without
      an [Unreleased] bullet, so its notes named only one — and this repo's own v0.1.38/v0.1.39 say
      just "Incremental release.")
      • Dashboard release fold now lists the commits between the previous tag and this one
        (/relapi compare, plumbing-filtered — land-merges/release-commits/devbumps hidden), capped at
        30 with a full-compare link. Works retroactively for every past release of every project.
      • Generated Forgejo release notes: the promote steps (pipeline-promote-tag +
        pipeline-promote-image) append a data-derived **Included changes** section (same plumbing
        filter) to the release body. Best-effort — a compare miss never fails a release.
    • Deploy target labels ("deploy → seanfarm"). An artifact deploy is a consumption by a carrier
      repo — the DEPLOY pane rows and the Latest·deploy card now name it (→ seanfarm), so the same
      artifact consumed by a different environment reads as a different deploy. pipectl status prints
      the target too. Display-only (the deploy records already carried carrierProject); gitops
      projects' own deploys are unchanged.
    Downloads
  • v0.1.39 2c74595626

    v0.1.39 Stable

    gitea_admin released this 2026-07-05 09:32:57 +00:00 | 2674 commits to trunk since this release

    Changed

    • Incremental release.
    Downloads