sean/pipelines
Watch
1
0
Fork
You've already forked pipelines
 0
Code Issues Pull requests 12 Projects Releases 294 Packages Wiki Activity
294 releases 294 tags
  • v0.1.124 c20645cbb8

    v0.1.124 Stable

    pipeline-bot released this 2026-07-10 11:40:17 +00:00 | 723 commits to main since this release

    • provision.sh: mc via apk add (no dl.min.io). The provisioner Job runs provision.sh on
      alpine/k8s (external overlay image) and already apk-adds gnupg; switch its dead dl.min.io mc fetch
      to apk add mc (Alpine mirror). templates/base is now fully off dl.min.io.

    • pkg-install: mc via a baked initContainer (no dl.min.io). The native-install test legs run
      stock distro images (debian/alma) that fetched mc from the now-dead dl.min.io. A pipeline-tools
      initContainer now copies baked mc into a shared /mcbin volume on the leg PATH. Last CWT off dl.min.io.

    Included changes (v0.1.123 -> v0.1.124)

    • 50eb579fddff fix(provisioner): provision.sh gets mc via apk, not dead dl.min.io
    • 78c0892c31b5 fix(pkg-install): provide mc via a pipeline-tools initContainer (drop dl.min.io)
    Downloads
  • v0.1.123 7c321894ec

    v0.1.123 Stable

    pipeline-bot released this 2026-07-10 11:28:29 +00:00 | 730 commits to main since this release

    • Fleet off dl.min.io: repoint the remaining mc-download trusted steps to baked images.
      dl.min.io's cert expired 2026-07-10, breaking every runtime curl … mc (exit 127). The 6
      git/curl/jq/mc(/kubectl/skopeo) steps (promote-image ×2, deploy-kernel, build-images gather,
      build-backfill, provisioner Job) now run on the baked pipeline-tools image; the 2 crane steps
      (promote-images, promote-kernel) run on sysadmin:v8 (crane+mc baked) — no runtime tool
      downloads. pkg-install + provisioner provision.sh (fixed/external images) follow via an
      mc initContainer.

    Included changes (v0.1.122 -> v0.1.123)

    • f198f5f7d7f6 fix(pipeline): repoint remaining mc-download steps off dead dl.min.io
    Downloads
  • v0.1.122 f1438f95d3

    v0.1.122 Stable

    pipeline-bot released this 2026-07-10 09:16:07 +00:00 | 735 commits to main since this release

    • promote-tag runs on the baked pipeline-tools image (no more dl.min.io). dl.min.io's TLS
      cert expired 2026-07-10, breaking the promote's runtime curl … mc download fleet-wide (exit 127).
      pipeline-promote-tag now runs on the new pipeline-tools image (git/curl/jq/mc baked, mc COPYed
      from the mirrored upstream image) — no runtime tool download. Durable replacement for the break-glass.

    Included changes (v0.1.121 -> v0.1.122)

    • 834c5f68b94a fix(promote-tag): run on baked pipeline-tools image (drop dl.min.io mc download)
    Downloads
  • v0.1.121 74d14a01be

    v0.1.121 Stable

    pipeline-bot released this 2026-07-10 08:59:56 +00:00 | 739 commits to main since this release

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

    Included changes (v0.1.120 -> v0.1.121)

    • 40da9b530f22 deploy(operator): pin pipelines-operator v0.1.26 -> v0.1.27
    Downloads
  • v0.1.120 5b1452ae54

    v0.1.120 Stable

    pipeline-bot released this 2026-07-10 07:22:49 +00:00 | 743 commits to main since this release

    • CI posts a pipeline/ci commit status to Forgejo. pipeline-build-buildkit (go-library-tag /
      go-operator-image) now posts state:success on the head sha after a green compile+publish, so branch
      protection can gate trunk merges on it (MED-S5). Best-effort (a Forgejo blip never false-reds a build);
      keyed to the exact built sha; holds the pipeline-bot token in a fixed curl step, preserving the
      untrusted/trusted split. First half of the maximum-repo-security workflow.

    Included changes (v0.1.119 -> v0.1.120)

    • 204c229c7b1d feat(pipelines): post pipeline/ci commit status to Forgejo on green build
    Downloads
  • v0.1.119 028e38c364

    v0.1.119 Stable

    pipeline-bot released this 2026-07-10 07:11:01 +00:00 | 747 commits to main since this release

    • Auto-deploy pipelines-operator pin. On a sean/pipelines-operator main push (a new
      operator release), the pipelines-operator-pindeploy Sensor fires pipeline-deploy-operator-pin,
      which idempotently bumps the operator app pin (targetRevision + controller image) in
      apps/applications.yaml, waits for CI green, merges to trunk, and ships a pipelines release —
      restoring the auto-deploy the flux->ArgoCD consolidation dropped, pipelines-operator-specifically
      (a bespoke CWT+Sensor, NOT the shared go-operator-image taxonomy).

    Included changes (v0.1.118 -> v0.1.119)

    • 6c21715160e6 feat(pipelines): auto-deploy pipelines-operator pin on operator release
    Downloads
  • v0.1.118 0eda3f98c0

    v0.1.118 Stable

    pipeline-bot released this 2026-07-09 21:47:42 +00:00 | 751 commits to main since this release

    • Deploy pipelines-operator v0.1.26 (cadence removed). Bump the operator app pin
      v0.1.25 -> v0.1.26. v0.1.26 drops the scheduled release-cadence cron (CRD Cadence/CadenceStyle
      fields + the cron-render partial); the operator prunes the now-unrendered <project>-release-cadence
      CronWorkflows on reconcile. Releases stay on-demand via pipectl ship.

    Included changes (v0.1.117 -> v0.1.118)

    • 8ea041d68f26 deploy(operator): pin pipelines-operator v0.1.25 -> v0.1.26 (cadence removed)
    Downloads
  • v0.1.117 9df9b9228c

    v0.1.117 Stable

    pipeline-bot released this 2026-07-09 18:41:11 +00:00 | 755 commits to main since this release

    • Release lands on trunk via fast-forward-only, not Do:merge (cadence removal, step 1). The
      release-prep step now merges the release: vX commit onto trunk with Do:fast-forward-only (under
      the {project}-merge mutex the release branch is a linear descendant, so ff-only always succeeds),
      so trunk ends at the release commit with no Merge PR 'release vX' merge commit. The released
      sha is the trunk tip, making promote's is-ancestor gate trivially true and removing the
      merge-commit shape a reverter could strand. Same ff-only idiom pipeline-promote/pipeline-deploy
      already use for push-protected branches. First step toward removing the scheduled-cadence concept
      entirely (releases are pipectl-driven).

    Included changes (v0.1.116 -> v0.1.117)

    • c071907568a1 fix(release): land the release commit on trunk via ff-only, not Do:merge
    Downloads
  • v0.1.116 e5ac73b30c

    v0.1.116 Stable

    pipeline-bot released this 2026-07-09 14:48:21 +00:00 | 760 commits to main since this release

    • Land step retries the Forgejo merge POST (REL-3). pipeline-merge did a single merge POST and
      exit 1 on any non-200, so a transient Forgejo 405 "Please try again later" (mergeability still
      computing async after the PR opens) permanently failed the land — the top land-failure signature
      (its siblings pipeline-promote/pipeline-deploy-flux already retried the identical call). It now
      retries with escalating backoff (8 attempts), stays bound to head_commit_id=${SHA} (a moved tip
      409s and fails fast, never merging an unvalidated commit), and short-circuits via the PR's merged
      flag if a prior POST already merged (idempotent — delete_branch_after_merge reaps the branch).
    • Remove the scheduled release-cadence cron (zerotea, hello-lib). Dropped spec.release.cadence
      from both PipelineProject CRs, so the operator prunes the <project>-release-cadence CronWorkflow
      (the fixed 6h auto-ship). Releases are now cut on demand via pipectl ship <project>; re-add the
      release: { cadence: "0 */6 * * *" } field to restore the timed auto-release later.

    Included changes (v0.1.115 -> v0.1.116)

    • ca4714234ec3 chore(cadence): remove the scheduled release-cadence cron (zerotea, hello-lib)
    • dd201e0670c2 fix(merge): retry the Forgejo merge POST on transient 405 (REL-3)
    Downloads
  • v0.1.115 6ad9c3cdab

    v0.1.115 Stable

    pipeline-bot released this 2026-07-09 13:04:00 +00:00 | 767 commits to main since this release

    • Switch the pipelines-operator app to the single-source config/seanfarm@v0.1.25 overlay (operator
      repo now owns Namespace + registry-pull-secret + netpol), replacing the interim multi-source app and
      deleting infra/operator-prereqs/. The operator release path was unblocked (the v0.1.25 release had
      been stranded by the Forgejo trunk-merge-revert race; a retry stuck).

    Included changes (v0.1.114 -> v0.1.115)

    • 12f9a0b57a93 chore(apps): operator app -> single-source config/seanfarm@v0.1.25
    Downloads