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.18 36cb703115

    v0.1.18 Stable

    gitea_admin released this 2026-07-03 12:53:43 +00:00 | 2788 commits to trunk since this release

    Changed

    • Dashboard: the Build / Release / Deploy panes now render from the
      pipelines-operator's projected Change CRs (PipelineBuild / PipelineRelease /
      PipelineDeploy) instead of the client-side parseWfRows run-classifier. A run's
      kind is decided ONCE, server-side, in the operator — so the misfiles are gone: a
      clean-VERSION build shows in Build (with releasable=true), never masquerading as
      a release; a dev delivery never appears in Release; plumbing runs project no CR
      at all (one central filter, not 13 per-sensor exclusion lists). The wf-poller
      publishes the CRs per project (/api/<proj>/{pbuild,prel,pdep}); the SPA parses them
      into the same row shape the panes/folds/latest-cards already use, and falls back to
      the classifier when a project has no CRs yet (cold rebuild before the operator syncs).
      Log/DAG folds keep working off each Change's status.workflow. Guarded by
      tests/dashboard-change-crs.test.js. See docs/CHANGE-MODEL.md.
    Downloads
  • v0.1.17 e67c148224

    v0.1.17 Stable

    gitea_admin released this 2026-07-03 12:23:41 +00:00 | 2797 commits to trunk since this release

    Changed

    • Incremental release.
    Downloads
  • v0.1.16 ee5560e313

    v0.1.16 Stable

    gitea_admin released this 2026-07-03 08:21:36 +00:00 | 2802 commits to trunk since this release

    Added

    • Dashboard: RELEASE rows now surface per-step logs for the credential-safe
      steps of a release run (compile/publish/test/validate/…). A succeeded release
      folds to its artifacts and step-log chips; a FAILED release folds to its
      step logs (the point of opening it). The promote/sign/devbump/cadence pods —
      which hold Forgejo push tokens + GPG/cosign signing keys — are never
      web-published: the wf-poller's logidx awk gates release nodes by a DEFAULT-DENY
      allowlist of safe step-template names (exact $7 in S match + NF==7
      field-integrity), the same templates already published for build runs. Because
      emit_logs only mirrors indexed S3 keys, a dropped step's log is never fetched.
      Guarded by tests/dashboard-release-logs.test.js (extracts the awk as the
      single source of truth; locks the render/render-installer boundary) +
      tests/dashboard-release-render.test.js. (Live release-log streaming remains a
      follow-up; this ships the archived path.)
    Downloads
  • v0.1.15 b58314ed8d

    v0.1.15 Stable

    gitea_admin released this 2026-07-02 22:13:38 +00:00 | 2807 commits to trunk since this release

    Added

    • Dashboard LIVE step logs: a running build/deploy row folds open to pulsing
      live chips; the log viewer auto-refreshes every 3s and sticks to the bottom —
      no Argo-UI detour to watch a run in flight. (wf-poller tails running pods into
      the shared volume; nginx serves /livelog/ + /api//live.)
    • Dashboard: "Latest · deploy" card in the DEPLOY PIPELINES pane (deployed
      commit, status, when), completing the latest-card trio.

    Changed

    • Dashboard: NOW RUNNING and RECENT RELEASES sections removed — running rows
      (pulsing dot + live chips) replace the stage pills, and release history lives
      one click away in Forgejo.

    Fixed

    • cancel-stale (the superseded-build reaper — plumbing, not signal) no longer
      appears anywhere on the dashboard: filtered from the archived log index, the
      live-log tails, and defensively at parse time.
    • Live logs (adversarial-review hardening): live-tail is now scoped to build +
      deploy runs only — release/promote/cadence/ship pod stdout (which can hold
      Forgejo tokens / signing material) is never web-published, matching the
      archived-log surface.
    • Live viewer no longer false-"step finished"s on a single transient 404: the
      poller swaps /shared/livelog by rename (µs gap, not a full rm -rf window), the
      per-project TSV publishes tmp+mv, and the client tolerates 3 consecutive
      misses before declaring a live stream ended.
    • Live viewer: generation-guarded fetches (a stale in-flight poll can no longer
      paint the wrong log or kill a newly-opened chip's timer); wfPoll drops results
      that resolve after a project switch; a running row's fold no longer flaps shut
      between steps (sticky last-good live index until the row goes terminal); a
      release fold survives the Running→Succeeded flip (stable state key).
    Downloads
  • v0.1.14 413af10acc

    v0.1.14 Stable

    gitea_admin released this 2026-07-02 22:06:42 +00:00 | 2813 commits to trunk since this release

    Fixed

    • Release machinery no longer leaves a FAILED CI row per release: every CI
      sensor now excludes release-cadence/<v> (mirrors _devbump//_promote/).
      The cadence CWT pushes that branch, PR-merges it, then deletes it seconds
      later; CI was firing on the push and racing the delete, so the build cloned
      an already-gone branch (fatal: Remote branch … not found). Applied to all
      13 versioned projects (gitops-flux seanfarm/platform are versionless → no
      cadence → exempt).
    • pipeline-land now deletes the feature branch after a successful merge
      (delete_branch_after_merge) — a landed branch is done, so it's reaped
      instead of accumulating on Forgejo. The branch-delete push (after==000…0)
      is already dropped by every CI filter, so no spurious build fires.
    Downloads
  • v0.1.13 e5462e7c93

    v0.1.13 Stable

    gitea_admin released this 2026-07-02 21:24:03 +00:00 | 2818 commits to trunk since this release

    Fixed

    • Fix-forward off v0.1.12: the Forgejo ff-race poisoned that version number
      (DB recorded the _promote PR merged, main never advanced, every retry
      no-op-merged), freezing the shared trunk at v0.1.11 for all agents. Skip to
      0.1.13; this release carries all staging work that was stuck behind it.
    Downloads
  • v0.1.11 70aaf0e26e

    v0.1.11 Stable

    gitea_admin released this 2026-07-02 20:51:01 +00:00 | 2827 commits to trunk since this release

    Fixed

    • promote-image sign step carries an explicit command (/ko-app/cosign): the
      Argo controller no longer needs a gcr.io entrypoint lookup at pod-creation
      time — that lookup bypasses every registry mirror and stranded releases
      whenever gcr.io throttled.
    Downloads
  • v0.1.10 029a42f8ec

    v0.1.10 Stable

    gitea_admin released this 2026-07-02 20:38:30 +00:00 | 2832 commits to trunk since this release

    Changed

    • Compile concurrency: the per-project compile mutex is now keyed
      {project}-{compileKey} (default compile = old behavior, REQUIRED for
      cachePatch/RWO-cache users like zelnet). zerotea's CI sensor passes the push
      sha as compileKey → unique mutex per run → a grind wave's builds run fully
      parallel. A 20-branch wave had run strictly serially behind the old
      unconditional mutex despite zerotea never mounting the cache PVC.
    • Builder renamed zelnet-builder → zig-builder:v1 (it is the shared zig
      toolchain: zelnet, zdns, zerotea). v1 bakes a prewarmed zig global cache
      (stdlib/compiler-rt for native Debug, -fllvm test binaries, and both musl
      ReleaseSafe cross targets) so parallel cacheless pods start warm, plus a
      debug toolbelt (ripgrep/file/tree/less/procps/xxd/patch). All consumers
      repinned (zerotea/zelnet sensors+config, seanfarm autoland, pipectl land).
    Downloads
  • v0.1.9 ad886b76fc

    v0.1.9 Stable

    gitea_admin released this 2026-07-02 19:01:53 +00:00 | 2838 commits to trunk since this release

    Added

    • pipectl + shipd resolve CR-registered projects: when a project has no
      projects/

      /config.yaml (the pipelines-operator world), config comes from
      its PipelineProject CR — hello-lib, the first CR-registered project, ships
      through both entrypoints. shipd gains get on pipelineprojects.

    Downloads
  • v0.1.8 1f7951c11c

    v0.1.8 Stable

    gitea_admin released this 2026-07-02 18:32:38 +00:00 | 2843 commits to trunk since this release

    Changed

    • zerotea staging sensor now fires ONLY on release commits (headmsg matches
      release-cadence/ or release: ): the release is ONE pipeline from staging
      that ff's main at the end. Ordinary lands fire nothing on staging — their
      gate is the feature branch's own CI. Fixes the land-batch stampede where 10
      merges stacked 10 concurrent pipeline-staging runs (2026-07-02).
    Downloads