sean/pipelines-operator
Watch
1
0
Fork
You've already forked pipelines-operator
 0
Code Issues Pull requests 3 Projects Releases 58 Packages Wiki Activity
58 releases 58 tags
  • v0.1.47 b7d603a9ec

    v0.1.47 Stable

    pipeline-bot released this 2026-07-21 18:12:32 +00:00 | 50 commits to main since this release

    • Registry pull secret flips to the bare registry store. config/seanfarm/registry-pull-secret.yaml repoints its
      secretStoreRef from zot-alice-registry-credentials → zot-registry-registry-credentials ahead of the XRegistry/alice
      teardown (pull is anonymous; repointed so the ExternalSecret stays healthy after alice is gone).
    • Deploys are GATED on release-green (universal, structural). The rendered <project>-deploy sensors
      (argocd/flux/ibmi taxonomies) now trigger on a new pipeline-release resource EventSource when the
      project's PipelineRelease reaches status.deployable==true — instead of on a git main-push. Because
      deployable latches true only when the WorkflowProjector observes the release-execution Workflow reach
      Succeeded (tag+sign+promote+ff-of-main done), a deploy can no longer start before its release is green
      (the prior main-push trigger raced ahead — main advances mid-release). The deploy consumes the release
      CR's spec.sha (the actually-shipped commit), and a deterministic <project>-deploy-<sha12> Workflow
      name dedups the EventSource's repeat status-update fires. New sensorSpec fields
      (EventSourceName/EventName/FilterFields/DeterministicName) default to the forgejo webhook so every
      build/staging/autoland sensor renders byte-identically. The pipeline-release EventSource + its RBAC ship
      in sean/pipelines bundle/workflows-infra-bare.

    Included changes (v0.1.46 -> v0.1.47)

    • 421abb0ff0b2 feat(deploy-gate): render -deploy sensors on release-deployable, not main-push
    • 1111113687f4 chore(registry): flip pull-secret store to zot-registry-registry-credentials
    Downloads