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.148 b1e3668108

    v0.1.148 Stable

    pipeline-bot released this 2026-07-13 07:50:43 +00:00 | 2105 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.147 -> v0.1.148)

    • 9e92aba0466d fix(provision): drop runtime mc/gnupg fetches — pipeline-tools bakes both
    Downloads
  • v0.1.147 14e322749f

    v0.1.147 Stable

    pipeline-bot released this 2026-07-13 07:42:07 +00:00 | 2109 commits to trunk since this release

    • Deploy pipelines-operator v0.1.30. Auto-bump the operator app pin (targetRevision + controller image) v0.1.29 -> v0.1.30 in apps/applications.yaml; rides the next pipelines release to main, where the pipelines-deploy sensor syncs the operator.

    Included changes (v0.1.146 -> v0.1.147)

    • 60b88c929f52 deploy(operator): pin pipelines-operator v0.1.29 -> v0.1.30
    Downloads
  • v0.1.146 06507d2c89

    v0.1.146 Stable

    pipeline-bot released this 2026-07-13 01:19:41 +00:00 | 2113 commits to trunk since this release

    Fixed

    • devbump self-certifies its version-bump commit (unblocks status-check-protected trunks). The
      "open next dev cycle" merge rides a CI-excluded _devbump/* branch, so it hit the same
      branchProtection.security.statusCheck block as release-prepare — pipeline/ci never posted a status,
      so the ff-merge 405'd, wedging every post-release devbump. The trusted devbump now posts
      pipeline/ci=success on its commit before merging, across all four sites (pipeline-devbump.yaml + the
      inline devbump in pipeline-promote{,-tag,-image}.yaml). Completes the release-path fix.

    Included changes (v0.1.145 -> v0.1.146)

    • 91b18777fc19 docs(changelog): note devbump self-certify fix
    • 7b2f22575ccd fix(devbump): self-certify the version-bump commit on CI-excluded branch
    Downloads
  • v0.1.145 f8837cb0f2

    v0.1.145 Stable

    pipeline-bot released this 2026-07-12 11:22:16 +00:00 | 2118 commits to trunk since this release

    Removed

    • Bootstrap alias pipeline-release-cadence removed. The cutover is complete — the operator now
      runs on pipeline-release-prepare, so the temporary old-named self-certifying alias is deleted.

    Included changes (v0.1.144 -> v0.1.145)

    • 3e25d9892e9f chore(cutover): remove temporary pipeline-release-cadence bootstrap alias
    Downloads
  • v0.1.144 8264639bad

    v0.1.144 Stable

    pipeline-bot released this 2026-07-12 11:12:57 +00:00 | 2122 commits to trunk since this release

    • Deploy pipelines-operator v0.1.29. Auto-bump the operator app pin (targetRevision + controller image) v0.1.28 -> v0.1.29 in apps/applications.yaml; rides the next pipelines release to main, where the pipelines-deploy sensor syncs the operator.

    Included changes (v0.1.143 -> v0.1.144)

    • 6412899939a8 deploy(operator): pin pipelines-operator v0.1.28 -> v0.1.29
    Downloads
  • v0.1.143 5b3397cd49

    v0.1.143 Stable

    pipeline-bot released this 2026-07-12 10:59:10 +00:00 | 2126 commits to trunk since this release

    Added

    • Temporary bootstrap alias pipeline-release-cadence — an old-named, self-certifying copy of
      pipeline-release-prepare so the still-running OLD operator can cut the ONE release that deploys the
      cadence-excised NEW operator; removed right after the operator cuts over. See cadence-excision cutover.

    Fixed

    • release-prepare self-certifies its version-bump commit (unblocks status-check-protected trunks).
      When a project's trunk enables branchProtection.security.statusCheck (contexts pipeline/ci),
      the release-prepare's ff-merge was rejected — its strip-dev + changelog commit rides a _release/*
      branch that is deliberately CI-excluded, so pipeline/ci never posts a status. The trusted
      release-prepare (Forgejo token, merge mutex, no project code) now POSTs pipeline/ci=success on
      that commit before merging — the same trust boundary as the ff-merge itself. Fixes a permanent
      release block on operator + package projects introduced by the max-security dials.

    Changed

    • Excise the "cadence" misnomer from the release engine. The scheduled-cron cadence is
      retired; the word lingered as the name of the live release-orchestration stage that
      pipectl ship drives. Renamed in lockstep with the operator: the
      pipeline-release-cadence CWT → pipeline-release-prepare, its release-cadence/
      version-bump branch → _release/ (adopting the _xxx/ plumbing convention), the
      <proj>-release-cadence purpose → -release-prepare, and the dashboard row-classifier +
      shipd VAP + linux CI sensor + docs to match. Stage 1 prepares the release (resolve
      version, promote changelog, ff-merge to trunk); stage 2 runs it. Retired the now-invalid
      "re-add release: { cadence: … } to restore" notes (the CRD field is gone). All dashboard
      guard tests + the TLA release contract model-check pass on the rename.

    Included changes (v0.1.142 -> v0.1.143)

    • d14b991e55bc chore(cutover): temporary self-certifying pipeline-release-cadence alias
    • 3b193c4d9b16 fix(release-prepare): self-certify version-bump commit on CI-excluded branch
    • 657b489006f7 refactor(release): excise 'cadence' misnomer (pipelines side)
    Downloads
  • v0.1.142 bd82c98ae1

    v0.1.142 Stable

    pipeline-bot released this 2026-07-12 09:36:56 +00:00 | 2134 commits to trunk since this release

    Changed

    • zdns/zig builder pins → AlmaLinux v3 (Phase 2c). All 7 pins move off the pre-Alma
      Debian builders to zdns-builder:v3 / zig-builder:v3 (AlmaLinux 10): the zdns build
      (project-crs/zdns.yaml), the zelnet + zerotea builds, the two zerotea guard crons, and
      the operator-pin merge image (bin/pipectl MERGE_BUILDER + pipeline-deploy-operator-pin
      mergeImage). Safe now that promote no longer rides builderImage (it's on
      debian-repo-signer), so the Alma builders — which have no apt-ftparchive on the compile
      path — can't break deb/rpm repo-signing. Verified live before the bump: zig-builder:v3 has
      every tool pipeline-merge invokes (bash/curl/git/jq/mc/sed) + zig/nfpm; zdns-builder:v3 is
      jq-less but its consumers (build/staging/pkg-install) invoke no jq. Completes the deb-path
      leg of AlmaLinux-everywhere: no pipeline step fetches a tool at run time.

    Included changes (v0.1.141 -> v0.1.142)

    • fd0ab5684830 feat(builders): zdns/zig builder pins -> AlmaLinux v3 (Phase 2c cascade)
    Downloads
  • v0.1.141 9ae59f263a

    v0.1.141 Stable

    pipeline-bot released this 2026-07-12 09:23:46 +00:00 | 2138 commits to trunk since this release

    Changed

    • promote runs on the baked debian-repo-signer image (Phase 2c). The TRUSTED
      deb+rpm repo-build+GPG-sign+publish step (pipeline-promote) moves off the project's
      compile builderImage onto a dedicated debian-repo-signer:v2 image with
      apt-ftparchive + createrepo-c + rpm + gnupg + jq + git + mc all baked — deleting the
      runtime apt-get install gnupg jq. Single-responsibility: project builders compile,
      this image builds+signs the repo. This also decouples promote from the builder so the
      next step (bumping zdns/zig builders to AlmaLinux, which lacks apt-ftparchive on the
      compile path) can't break deb/rpm repo-signing. Image validated end-to-end (apt Release
      clearsign/detach, createrepo_c indexes real rpm headers, all promote coreutils present).

    Included changes (v0.1.140 -> v0.1.141)

    • 2645a005c4ff feat(promote): run release step on baked debian-repo-signer (Phase 2c)
    Downloads
  • v0.1.140 ee6581998c

    v0.1.140 Stable

    pipeline-bot released this 2026-07-12 08:31:07 +00:00 | 2142 commits to trunk since this release

    Changed

    • pipelines-ci → v4 (AlmaLinux) (Phase 2c). The self-hosting pipelines validate
      builder (kustomize dry-run + TLA model-check) moves off the pre-Alma image to
      pipelines-ci:v4. Verified on the Alma image before shipping: real kubectl kustomize
      renders and TLC model-checks a spec clean (it's the CI system's own builder).

    Included changes (v0.1.139 -> v0.1.140)

    • 2514000c9303 feat(cascade): pipelines-ci v1->v4 (AlmaLinux) — verified kustomize+TLC first
    Downloads
  • v0.1.139 02b9bda26f

    v0.1.139 Stable

    pipeline-bot released this 2026-07-12 07:59:20 +00:00 | 2146 commits to trunk since this release

    Changed

    • Consumer cascade (Phase 2c, part 1). Repoint cast-render (v2→v4, in
      pipeline-test-ibmi-behavioral) and ibmi-builder (v8→v9, the 4 rpg CRs) to their
      released AlmaLinux images (tag+digest). Makes those Alma builds actually used.
      pipelines-ci + the zdns/zig-builder deb-cascade (needs the Debian repo-signer
      first) follow separately.

    Included changes (v0.1.138 -> v0.1.139)

    • 3fe4485ea60f feat(cascade): cast-render v4 + ibmi-builder v9 consumers to AlmaLinux (Phase 2c pt1)
    Downloads