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.118 0eda3f98c0

    v0.1.118 Stable

    pipeline-bot released this 2026-07-09 21:47:42 +00:00 | 2240 commits to trunk 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 | 2244 commits to trunk 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 | 2249 commits to trunk 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 | 2256 commits to trunk 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
  • v0.1.114 ed61b508de

    v0.1.114 Stable

    pipeline-bot released this 2026-07-09 12:43:55 +00:00 | 2261 commits to trunk since this release

    • Merge the operator's prereqs into the operator app via a multi-source Application: pipelines-operator
      now has two sources — the operator's config/default (unchanged) plus this repo's
      infra/operator-prereqs (Namespace + registry-pull-secret + netpol) — so one app owns all of
      pipelines-operator-system, retiring the separate pipelines-operator-prereqs app. ArgoCD tiles:
      6 → 5. (A single-source config/seanfarm overlay already exists on the operator trunk for a cleaner
      consolidation once the operator release path is unblocked.)

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

    • 0a1003c26a92 chore(apps): merge operator prereqs into the operator app via multi-source (6->5)
    Downloads
  • v0.1.113 d66c773147

    v0.1.113 Stable

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

    • Consolidate the scattered workflows-alice ArgoCD apps: a new bundle/workflows-infra
      aggregating kustomization unions project-crs + infra/build-pipeline + projects/linux,
      delivered by ONE pipeline-workflows-infra Application (SSA-adopts the live objects, no
      churn). Retires the pipeline-projects ApplicationSet and the separate pipeline-project-crs
      • build-pipeline Applications. ArgoCD tiles: 8 → 6.

    Included changes (v0.1.112 -> v0.1.113)

    • c0552343ac99 chore(apps): consolidate workflows-alice infra into one pipeline-workflows-infra App
    Downloads
  • v0.1.112 bb96b4643a

    v0.1.112 Stable

    pipeline-bot released this 2026-07-09 11:27:44 +00:00 | 2271 commits to trunk since this release

    • Fold the app-of-apps ArgoCD config into this repo under apps/ (the pipelines
      AppProject + child Applications + repo Secrets), retiring the standalone
      sean/pipelines-argocd repo so the ArgoCD delivery config is pipeline-managed
      like everything else. The flux root-App seed now sources sean/pipelines. CI
      validate renders apps/ too.

    Included changes (v0.1.111 -> v0.1.112)

    • 00fed930e6ee chore(apps): fold pipelines-argocd app-of-apps config into apps/
    Downloads
  • v0.1.111 44da2abf59

    v0.1.111 Stable

    pipeline-bot released this 2026-07-09 09:49:10 +00:00 | 2277 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.110 -> v0.1.111)

    • c6287c3516b9 fix(deploy-flux): grace transient Ready=False instead of failing instantly
    Downloads
  • v0.1.110 54a24ff861

    v0.1.110 Stable

    pipeline-bot released this 2026-07-09 09:33:10 +00:00 | 2282 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.109 -> v0.1.110)

    • c4e29afdbc7f fix(deploy-flux): stop SIGPIPE (exit 141) aborting gitops-flux deploys
    Downloads
  • v0.1.109 def43f8342

    v0.1.109 Stable

    pipeline-bot released this 2026-07-09 09:02:57 +00:00 | 2287 commits to trunk since this release

    Changed

    • Incremental release.

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

    • f4b0e4cce8c6 fix(prereqs): registry-pull-secret store zot-dev -> zot-alice (stale tenant name)
    Downloads