sean/pipelines
Watch
1
0
Fork
You've already forked pipelines
 0
Code Issues Pull requests 12 Projects Releases 282 Packages Wiki Activity
282 releases 282 tags
  • v0.1.232 7c0663a4bb

    v0.1.232 Stable

    pipeline-bot released this 2026-07-21 19:16:17 +00:00 | 214 commits to main since this release

    • Deploy pipelines-operator v0.1.46 → v0.1.48. Carries the universal deploy-gate: the operator now renders
      <project>-deploy sensors on the pipeline-release resource EventSource (fire on deployable==true, not
      main-push) with the bool release filter, plus the registry pull-secret overlay repointed to
      zot-registry-registry-credentials (XRegistry/alice teardown). (The auto pin-bump via pindeploy failed on a
      transient forgejo merge flake; bumped by hand — the documented manual operator-deploy path.)

    Included changes (v0.1.231 -> v0.1.232)

    • 39475c02fc10 deploy(operator): pin pipelines-operator v0.1.46 -> v0.1.48
    Downloads
  • v0.1.231 9b6c7dc9f2

    v0.1.231 Stable

    pipeline-bot released this 2026-07-21 18:34:47 +00:00 | 218 commits to main since this release

    • Fix pindeploy release filter (bool). pipelines-operator-pindeploy compared deployable == "true"
      (string) but the CR field is a bool → the deployable=true event never matched. Now
      (deployable == true || deployable == "true").

    Included changes (v0.1.230 -> v0.1.231)

    • 925c0965755d fix(deploy-gate): compare deployable as bool in pindeploy filter
    Downloads
  • v0.1.230 a04519905b

    v0.1.230 Stable

    pipeline-bot released this 2026-07-21 17:58:14 +00:00 | 222 commits to main since this release

    • Deploy-gate trigger source: pipeline-release resource EventSource. New bundle/workflows-infra-bare/release-eventsource.yaml
      — a resource EventSource watching PipelineRelease CRs (ADD/UPDATE, afterStart: true) + its reader SA/Role/RoleBinding. This is
      the source the operator-rendered <project>-deploy sensors (and the pipelines-operator-pindeploy sensor) gate on: a deploy
      fires only when the project's release reaches status.deployable==true, never on a git main-push (which advances mid-release).
      pipelines-operator-pindeploy is rewired off forgejo/main-push onto pipeline-release/deployable (filter
      project == "pipelines-operator" && deployable == "true") with a deterministic pipelines-operator-pindeploy-<sha12> name for
      dedup — so the operator self-pin can no longer bump to an unsigned/unverified image. Pairs with pipelines-operator's rendered
      deploy-sensor rewire.

    Included changes (v0.1.229 -> v0.1.230)

    • 5f20e19731c3 feat(deploy-gate): pipeline-release EventSource + gate pindeploy on release-green
    Downloads
  • v0.1.229 95688d068c

    v0.1.229 Stable

    pipeline-bot released this 2026-07-21 16:45:25 +00:00 | 226 commits to main since this release

    • Bare registry self-mints its admin credential (severs registry-alice). The
      registry namespace now generates its own zot admin password (ESO Password
      generator → generator-backed htpasswd ExternalSecret, refreshInterval: "0" so
      it stays stable) and exposes it cluster-wide via a new
      zot-registry-registry-credentials ClusterSecretStore (own reader SA/Role/RoleBinding),
      replacing the cross-namespace zot-alice-registry-credentials store from
      XRegistry/alice. The workflows CI push creds (registry-credentials,
      zot-admin-credentials) repoint to the new store, and the in-cluster push host
      in the dockerconfig moves zot.registry-alice.svc → zot.registry.svc. Part of
      the XRegistry/alice teardown; the admin password rotates at this cutover (pushes
      only — pulls are anonymous).

    Included changes (v0.1.228 -> v0.1.229)

    • 19e28a0cd1c9 feat(registry): self-mint bare zot admin cred + flip workflows CI push off alice store
    Downloads
  • v0.1.228 29cbfdc564

    v0.1.228 Stable

    pipeline-bot released this 2026-07-21 15:56:25 +00:00 | 230 commits to main since this release

    • Dashboard: click the SHA for the diff, click the red failed-step for the log. A build/deploy row's commit now links to the Forgejo commit DIFF (what changed), and the red "failed at " pill opens the step's mirrored log INLINE (logbox) instead of only linking to Argo (Argo stays as the fallback when the log isn't mirrored yet).

    • Remove the dashboard publishing release sub-state. It was a cosmetic relabel of a Running release that had a matching deploy — but the real fix is to not START the deploy until the release is green (deploy retriggers on release Deployable), so the state it papered over no longer occurs. Dropped the panesRows marking + rowHtml relabel + tests/dashboard-publishing.test.js + its validate-guard line.

    Included changes (v0.1.227 -> v0.1.228)

    • ac5d52a6b150 fix(dashboard): remove 'publishing' sub-state; SHA->diff + red failed-step->inline log
    Downloads
  • v0.1.227 d1d1418f2a

    v0.1.227 Stable

    pipeline-bot released this 2026-07-21 14:28:10 +00:00 | 234 commits to main since this release

    • Deploy pipelines-operator v0.1.46 (deploy-gate live). Roll the operator with the DeploySubmitter gate: a declared deploy is held Pending until its release latches Deployable (Succeeded), so no deploy starts before its release goes green.

    Included changes (v0.1.226 -> v0.1.227)

    • eb6cac763f9e chore(deploy): pipelines-operator v0.1.45 -> v0.1.46 (deploy-gate live, recut off trunk)
    Downloads
  • v0.1.226 f5f900ac86

    v0.1.226 Stable

    pipeline-bot released this 2026-07-21 14:22:50 +00:00 | 238 commits to main since this release

    • Registry flip step 2: bare registry.sean.farm routes + buildkit mirror → bare zot. Add the registry +
      registry-https-redirect HTTPRoutes to bundle/registry (ns registry, parenting the portal-alice gateway
      listeners widened in platform v0.1.68); /v2/ + catch-all both backend the local bare zot (same-ns, no
      ReferenceGrant). During overlap with the still-present registry-alice route, Gateway-API awards /v2/ to the older
      alice route; both zots serve the same alice-zot bucket, so pulls are identical until the alice route is removed
      (step 3). Also repoint bundle/buildkit registry mirror (docker.io/gcr.io) from zot.registry-alice.svc →
      zot.registry.svc. The OIDC-gated UI (oathkeeper + zot openid) is a deferred follow-on — zot already allows
      anonymous read, so the UI browses read-only and /v2/ pulls are unaffected.

    Included changes (v0.1.225 -> v0.1.226)

    • d627c637d30a feat(registry): bare registry.sean.farm routes + buildkit mirror flip (registry flip step 2)
    Downloads
  • v0.1.225 b04f1a38bf

    v0.1.225 Stable

    pipeline-bot released this 2026-07-21 13:17:31 +00:00 | 242 commits to main since this release

    Changed

    • Incremental release.

    Included changes (v0.1.224 -> v0.1.225)

    • 5d74e5d1c951 fix(registry): registry-scoped MinIO creds store (unblock zot ES sync)
    • b66d186897ed fix(registry): whitelist StatefulSet in pipelines AppProject
    Downloads
  • v0.1.224 f9e87927a2

    v0.1.224 Stable

    pipeline-bot released this 2026-07-21 12:49:17 +00:00 | 247 commits to main since this release

    • Bare registry zot singleton (additive) — CI-spine collapse. New bundle/registry + registry ArgoCD
      app (argocd-platform) stand up a bare zot OCI registry in namespace registry, replacing per-tenant
      XRegistry/alice (registry-alice). It points at the SAME alice-zot MinIO bucket (zero data migration;
      the kernel image spine registry.sean.farm/seanfarm/{linux-kernel,node-bootc,zfs-userspace} is already
      there) and sources admin-htpasswd parity cross-namespace from the zot-alice-registry-credentials
      ClusterSecretStore. ADDITIVE: runs alongside registry-alice, nothing repoints — OIDC (UI) + the
      registry.sean.farm HTTPRoutes are omitted here (all /v2/ image traffic is htpasswd + anonymous read) and
      are wired at the flip, when the route + shipwright/buildkit mirrors move to zot.registry.svc. Added
      registry to the pipelines AppProject destinations.

    Included changes (v0.1.223 -> v0.1.224)

    • 3f158d5970c2 feat(registry): bare zot OCI registry singleton (additive, same alice-zot bucket)
    Downloads
  • v0.1.223 e296db9a57

    v0.1.223 Stable

    pipeline-bot released this 2026-07-21 11:36:15 +00:00 | 251 commits to main since this release

    • Dashboard: "publishing" release sub-state. A release fires its deploy via ff_main — which happens after its tests
      pass — then lingers Running only through tag/devbump/projector-reconcile bookkeeping. Showing that tail as Running
      next to a Running deploy read as "deploying before tested" (it isn't). The releases pane now relabels a Running release
      to publishing once a deploy for the same sha exists (deploy.sha === release.sha; gitops deploys carry no version, so
      sha is the key). Never masks a stuck or failed row. New tests/dashboard-publishing.test.js (registered in the validate guard).

    Included changes (v0.1.222 -> v0.1.223)

    • 2fc51c15174a feat(dashboard): 'publishing' release sub-state (ff_main tail)
    Downloads