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.42 c3fea2a9c4

    v0.1.42 Stable

    gitea_admin released this 2026-07-05 10:21:45 +00:00 | 1121 commits to main 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 | 1127 commits to main 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 | 1132 commits to main 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 | 1137 commits to main since this release

    Changed

    • Incremental release.
    Downloads
  • v0.1.38 09e3037e4e

    v0.1.38 Stable

    gitea_admin released this 2026-07-05 09:03:29 +00:00 | 1142 commits to main since this release

    Changed

    • Incremental release.
    Downloads
  • v0.1.37 a2b0750b57

    v0.1.37 Stable

    gitea_admin released this 2026-07-05 07:31:35 +00:00 | 1147 commits to main since this release

    Added

    • Trace front-door (change traceability, Phase C). Follow a change through build -> release ->
      deploy from either surface:
      • pipectl trace <project> <ref> where <ref> is a commit sha, vX.Y.Z, a Forgejo
        /commit/<sha> permalink, or file:line (runs git blame in the cwd / PIPECTL_REPO). Joins
        the Build/Release/Deploy CRs by commit and reports the chain, incl. the first tagged release
        containing a non-release commit (Forgejo compare ancestry) and each deploy's carrier +
        change-range. pipectl status now reads the same Change CRs (latest build/release/deploy)
        instead of scraping raw workflows.
      • Deploy rows/trace now show "carried by seanfarm@" — the pdep poller +
        parsePDep carry carrierProject/carrierSha, so an operator's artifact deploy links to the
        seanfarm commit that moved its Flux pin (previously CLI-only).
      • Dashboard "trace" header link -> a panel that resolves the same refs and renders the chain
        for the selected project (client-side join over the pane data + /relapi for containment).
    Downloads
  • v0.1.36 974c6aa416

    v0.1.36 Stable

    gitea_admin released this 2026-07-04 23:12:05 +00:00 | 1152 commits to main since this release

    Changed

    • Incremental release.
    Downloads
  • v0.1.35 b4c7708f33

    v0.1.35 Stable

    gitea_admin released this 2026-07-04 22:32:46 +00:00 | 1158 commits to main since this release

    Changed

    • Retire projects/{openbao,forgejo,kratos-identity}-operator/ — now PipelineProject CRs in seanfarm
      (with spec.deploy.pin), completing the operator migration begun with pipelines-operator. Parity-gated
      render + preserveResourcesOnDeletion keep their sensors alive through the cutover.
    Downloads
  • v0.1.34 c9472b4e2e

    v0.1.34 Stable

    gitea_admin released this 2026-07-04 22:18:30 +00:00 | 1163 commits to main since this release

    Changed

    • Retire projects/pipelines-operator/ — the project is now a PipelineProject CR in seanfarm
      (pipeline-projects/pipelines-operator.yaml, with spec.deploy.pin). The operator renders the same
      objects (parity-gated) and SSA-adopts the preserved sensors; the ApplicationSet's
      preserveResourcesOnDeletion keeps them alive through the cutover. First of the operator migrations.
    Downloads
  • v0.1.33 8a4ab038a4

    v0.1.33 Stable

    gitea_admin released this 2026-07-04 21:08:06 +00:00 | 1169 commits to main since this release

    Fixed

    • Left-nav dot no longer shifts the labels. The "moving" dot moved to an absolute pseudo-element in
      the existing left padding, so project labels (incl. wrapped ones like kratos-identity-operator) keep
      their original alignment; the dot only appears when the project is running.
    Downloads