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.38 09e3037e4e

    v0.1.38 Stable

    gitea_admin released this 2026-07-05 09:03:29 +00:00 | 2679 commits to trunk 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 | 2684 commits to trunk 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 | 2689 commits to trunk 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 | 2695 commits to trunk 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 | 2700 commits to trunk 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 | 2706 commits to trunk 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
  • v0.1.32 87d7e4121f

    v0.1.32 Stable

    gitea_admin released this 2026-07-04 20:47:20 +00:00 | 2711 commits to trunk since this release

    Added

    • Left-nav "moving" indicator. Each project in the sidebar now shows a pulsing blue dot when it
      has a Running/Pending pipeline (any Build/Release/Deploy/ship) right now — an at-a-glance view of
      what's active across the fleet without clicking in. The wf-poller emits /shared/active.txt
      (projects with a running workflow, recomputed each 6s cycle from the fleet-wide wf list); nginx
      serves it at /api/active; the SPA polls it every 5s and toggles a .running class. Distinct
      from the .active (selected-project) highlight — a project can be selected, moving, both, or neither.
    Downloads
  • v0.1.31 bf3777e50b

    v0.1.31 Stable

    gitea_admin released this 2026-07-04 20:33:57 +00:00 | 2716 commits to trunk since this release

    Changed

    • docs/CHANGE-MODEL.md documents the deploy-provenance chain closure (fromSha/version/
      releaseRef/outcome, requestedBy/image) and the new retention caps (builds 50, deploys 400,
      releases 500).
    Downloads
  • v0.1.30 73659f8f92

    v0.1.30 Stable

    gitea_admin released this 2026-07-04 20:18:39 +00:00 | 2722 commits to trunk since this release

    Added

    • "Which changes did this deploy include" (end-to-end traceability, Phase A). The deploy
      templates now emit provenance as Argo output params for the pipelines-operator to project onto
      PipelineDeploy.status:
      • pipeline-deploy (gitops-deploy) and pipeline-deploy-flux (gitops-flux) write fromSha
        (the previously-deployed tip — pipeline-deploy takes it from the push's body.before via a
        new sensor param; the flux twin captures the pre-ff main tip in-workflow), version (the
        release tag pointing at the deployed sha, resolved via the Forgejo tags API), and outcome
        (deployed/superseded/failed/rolled-back, written at each exit).
    • Dashboard: a deploy row now folds open to the commits it shipped — a Forgejo compare
      (fromSha...sha) rendered as "N changes since <short>" with per-commit links + a full-compare
      link. A deploy row also shows a version chip when the deployed commit is a tagged release, and
      the Deploy card reflects outcome (a superseded deploy reads "superseded", not a bare
      "Succeeded"). Release rows carry the new requestedBy/image data. All additive: the panes'
      uniform identity (build/deploy lead with a 12-char sha, release with vX.Y.Z) is unchanged.

    Fixed

    • devbump + release-cadence reap their branches on merge. pipeline-devbump and
      pipeline-release-cadence now pass delete_branch_after_merge: true on the PR merge, so
      _devbump/*-dev and release-cadence/* branches no longer pile up on Forgejo after every
      dev-cycle open / release (matching pipeline-land's feature-branch reap; the promotes already
      explicit-DELETE their _promote/*/_devbump/v* temps). The ffpr main-advance merges are
      deliberately left untouched — their head is trunk, which must never be deleted.
    Downloads
  • v0.1.29 a59960ed30

    v0.1.29 Stable

    gitea_admin released this 2026-07-04 11:08:40 +00:00 | 2728 commits to trunk since this release

    Fixed

    • devbump + release-cadence reap their branches on merge. pipeline-devbump and
      pipeline-release-cadence now pass delete_branch_after_merge: true on the PR merge, so
      _devbump/*-dev and release-cadence/* branches no longer pile up on Forgejo after every
      dev-cycle open / release (matching pipeline-land's feature-branch reap; the promotes already
      explicit-DELETE their _promote/*/_devbump/v* temps). The ffpr main-advance merges are
      deliberately left untouched — their head is trunk, which must never be deleted.
    Downloads