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.108 e1f6667a7a

    v0.1.108 Stable

    pipeline-bot released this 2026-07-09 08:29:11 +00:00 | 2292 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.107 -> v0.1.108)

    • 7d0b15378373 fix(build-pipeline): manage cosign-key-extractor Job as an ArgoCD Sync hook
    Downloads
  • v0.1.107 16d0ec2716

    v0.1.107 Stable

    pipeline-bot released this 2026-07-09 08:18:52 +00:00 | 2297 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.106 -> v0.1.107)

    • b807266ec473 feat: home build-pipeline-base for the ArgoCD migration (de-templated to alice)
    Downloads
  • v0.1.106 42e1078ed8

    v0.1.106 Stable

    pipeline-bot released this 2026-07-09 07:13:25 +00:00 | 2302 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.105 -> v0.1.106)

    • 51e9559888f8 feat: home the pipeline-project CRs + operator prereqs for the ArgoCD migration
    Downloads
  • v0.1.105 36aba11114

    v0.1.105 Stable

    pipeline-bot released this 2026-07-09 02:34:16 +00:00 | 2308 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.104 -> v0.1.105)

    • 415a327f19ed feat(templates): pipeline-test-envtest — a real go-operator/go-library test gate
    Downloads
  • v0.1.104 4784a606e9

    v0.1.104 Stable

    pipeline-bot released this 2026-07-08 17:13:23 +00:00 | 2313 commits to trunk since this release

    • Enforce the CD ordering invariants that were previously branch-protection convention.
      I1: pipeline-staging now runs an assert-releasable step (new pipeline-assert-ready
      ClusterWorkflowTemplate, read-only pipeline-gate SA) that reads the trunk-tip's
      PipelineBuild.status.releasable before test+promote — no Release for a non-releasable
      Build. I2: pipeline-deploy gates the roll on the released PipelineRelease being
      Deployable (deployable latch, or phase==Succeeded during the projector rollout) — no
      Deploy for a non-deployable Release. Both are lenient on a missing CR (branch protection
      stays primary) and strict on an explicit violation.
    • Revive the ordering contract as a gated TLA+ spec: spec/release.tla
      (ReleasedImpliesReleasable ≈ I1, DeployedImpliesDeployable ≈ I2, with GateRelease/
      GateDeploy teeth), now model-checked in CI by spec/check.sh.

    Included changes (v0.1.103 -> v0.1.104)

    • c5b18442e6ec fix(cd): I2 gate must not false-fail on the mid-release deploy timing
    • c250d00d7f80 feat(cd): enforce the ordering invariants (I1 releasable, I2 deployable)
    Downloads
  • v0.1.103 88664b4a75

    v0.1.103 Stable

    pipeline-bot released this 2026-07-08 16:14:32 +00:00 | 2319 commits to trunk since this release

    Changed

    • Renamed the pipeline verb land → merge (Principle of Least Surprise — "merge my pull
      request"). pipectl merge <project> <branch> (and make merge) ff-merge a green feature branch
      onto trunk; pipectl land now errors with a redirect. Internals renamed for consistency: the
      ClusterWorkflowTemplate pipeline-land → pipeline-merge, the <proj>-land mutex/purpose/
      workflow-name → <proj>-merge (mutex kept in lockstep with pipeline-release-cadence so merge and
      ship still serialize). The autoland image-bump feature keeps its name; the dashboard isPlumbing
      filter is unchanged (it anchors on "Merge pull request", not the PR title).

    Included changes (v0.1.102 -> v0.1.103)

    • 1f325d965eff refactor(pipeline): rename the verb land -> merge (Principle of Least Surprise)
    Downloads
  • v0.1.102 9134c5bded

    v0.1.102 Stable

    pipeline-bot released this 2026-07-08 14:33:04 +00:00 | 2325 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.101 -> v0.1.102)

    • 86c4e0b77f82 feat(zelnet-gate): CLI error-handling assertions in the release functional gate
    Downloads
  • v0.1.101 ecb504c691

    v0.1.101 Stable

    pipeline-bot released this 2026-07-08 13:03:49 +00:00 | 2330 commits to trunk since this release

    Changed

    • Log-fold window tuned 200 -> 60. 200 (attempted "all retained builds") made the poller's durable
      fallback do ~3600 per-workflow MinIO listings per cycle and crawl; 60 covers the visible pane +
      scroll while keeping the poller responsive. (Unbounded log coverage needs a single recursive
      listing or a persistent /shared cache — follow-up.)

    Included changes (v0.1.100 -> v0.1.101)

    • 37386948c3d8 fix(dashboard): log window 200->60 (per-wf mc-ls cost crawled the poller)
    Downloads
  • v0.1.100 73120f0f35

    v0.1.100 Stable

    pipeline-bot released this 2026-07-08 12:54:42 +00:00 | 2335 commits to trunk since this release

    Changed

    • Build folds now show BOTH artifacts and logs for recent builds. The download-mirror window is
      sorted by build time (.status.finishedAt) instead of CR-creation time, so backfilled CRs
      (created at backfill time) no longer push genuinely-recent commits out of the newest-24 window.
    • Build/deploy logs now appear in every retained build's dropdown: the poller log window widened
      40 → 200 (the operator's build-retention). Logs are tiny text and the poller already resolves a
      GC'd workflow's logs from the immutable MinIO archive, so this is ~tens of MB (the download
      mirror stays disk-bound at 24).

    Included changes (v0.1.99 -> v0.1.100)

    • 78ffaa0181aa feat(dashboard): logs in every dropdown + time-sorted download window
    Downloads
  • v0.1.99 2987f62ace

    v0.1.99 Stable

    pipeline-bot released this 2026-07-08 12:26:22 +00:00 | 2341 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.98 -> v0.1.99)

    • 6a880969d0bc fix(dashboard): revert build-dl window 40->24 (node-root DiskPressure)
    Downloads