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.143 5b3397cd49

    v0.1.143 Stable

    pipeline-bot released this 2026-07-12 10:59:10 +00:00 | 637 commits to main 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