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.68 f20cae186f

    v0.1.68 Stable

    gitea_admin released this 2026-07-05 18:48:28 +00:00 | 2506 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.67 -> v0.1.68)

    • 1778760aa06a fix(builder-images): provision the read MinIO key (build read)
    Downloads
  • v0.1.67 18a1e7de66

    v0.1.67 Stable

    gitea_admin released this 2026-07-05 18:38:50 +00:00 | 2511 commits to trunk since this release

    Changed

    • CHANGE-MODEL Phase 2 ("declare intent") — actor side. pipectl ship and shipd's Ship
      button now CREATE a declared PipelineRelease CR (declaredBy: pipectl|shipd,
      requestedBy identity) instead of constructing a cadence Workflow — the pipelines-operator's
      ReleaseSubmitter owns workflow submission. pipectl ship --wait waits on the CR's phase
      (Succeeded/Skipped/Failed). shipd's RBAC shrinks to create-pipelinereleases (workflow
      construction removed; guarded by the shipd-release-guard VAP in seanfarm).
    • pipeline-release-cadence emits its verdict as output params (outcome: released|skipped,
      version, sha) so the operator can fill the declared CR and submit the release execution
      with explicit params. Inert on the legacy sensor path.
    • pipeline-staging accepts declared-intent audit params mode/version (empty on the
      sensor path); the run's gating still cross-checks via the build's computed mode until Phase 3.
    • New tests/shipd-release-create.test.js pins the shipd contract (declared CR, no workflow
      construction); added to the validate template's test list.

    Included changes (v0.1.66 -> v0.1.67)

    • dab0230b9a93 feat(change-model): Phase 2 actors declare intent — pipectl/shipd create PipelineRelease, cadence verdict outputs, staging audit params
    Downloads
  • v0.1.66 7c5d663545

    v0.1.66 Stable

    gitea_admin released this 2026-07-05 18:05:05 +00:00 | 2517 commits to trunk since this release

    Changed

    • The red failed-step pill IS the Argo link now — click promote ✗ itself, not a separate
      "open in Argo" word. The pill (from the v0.1.64 failed-release marker) is an <a> to the failed
      run; "credential step — log withheld · open in Argo →" stays as muted context. Degrades to a
      plain non-link span when the CR carries no workflow (cold rebuild).

    Included changes (v0.1.65 -> v0.1.66)

    • 89f03940a99f fix(dashboard): the red failed-step pill IS the Argo link
    • 8e97962a8881 fix(builder-images): no jq in build legs (buildkit + mc images lack it)
    Downloads
  • v0.1.65 95f6de17b2

    v0.1.65 Stable

    gitea_admin released this 2026-07-05 17:52:02 +00:00 | 2524 commits to trunk since this release

    Changed

    • Incremental release.

    Included changes (v0.1.64 -> v0.1.65)

    • d4d849dc0ceb fix(builder-images): clone with the admin token (forgejo-clone-secret absent in workflows-alice)
    Downloads
  • v0.1.64 7a4a24a224

    v0.1.64 Stable

    gitea_admin released this 2026-07-05 17:38:53 +00:00 | 2529 commits to trunk since this release

    Added

    • A Failed release now shows WHERE it died, even when that step's log is credential-gated. A
      release run's promote/sign/devbump steps hold Forgejo push tokens + signing keys, so their
      logs are default-denied from the dashboard's credential-safe allowlist — which left a Failed
      release showing only its green safe-step chips (validate/guard/publish) with nothing marking
      the failure. The fold now renders a red, non-clickable "failed at <step> — credential step, log
      withheld · open in Argo →" marker, driven by the query service's ReleaseLeg.failedStep (from
      PipelineRelease.status.failedStep, projected server-side by pipelines-operator — a step NAME,
      never log bytes). panesRows carries it; the marker is suppressed when the failing step is itself
      a published safe chip (its own red chip already shows it), and a credential-step failure with no
      safe log is now foldable so the marker still surfaces.

    Included changes (v0.1.63 -> v0.1.64)

    • f489f96fbbea feat(dashboard): mark WHERE a Failed release died (credential-gated step)
    • c0bff075a858 feat(builder-images): PipelineProject with fast parallel fleet builds (dockerfile-set)
    Downloads
  • v0.1.63 536b7a56cc

    v0.1.63 Stable

    gitea_admin released this 2026-07-05 17:11:10 +00:00 | 2536 commits to trunk since this release

    Changed

    • Panes read the query service; the poller TSV projections are retired (the last client copy of
      the join).       The Build/Release/Deploy panes now fetch GET /pipeapi/panes?project=&limit=100
      (the query service's per-project Change-CR feed, pipelines-operator ≥ the release after v0.1.8)
      mapped by a pure panesRows into the same row shape — deleting the wf-poller's
      pbuild/prel/pdep kubectl+go-template blocks, their nginx /api/<proj>/pbuild|prel|pdep
      locations, and the SPA's parsePBuild/parsePRel/parsePDep. The wf-row classifier fallback is
      unchanged (cold rebuild / service unreachable → panes fall back to wf-<proj>.tsv).
      tests/dashboard-change-crs.test.js rewritten to lock the panesRows contract (clean-VERSION
      build stays a Build, sparse omitempty legs default safely, empty feed → fallback).

    Included changes (v0.1.62 -> v0.1.63)

    • 1c2c2f3da52b Merge remote-tracking branch 'origin/trunk' into feat/panes-service-repoint
    • 37bb367c4343 feat(ci): model-check the deploy TLA contract in CI (pipelines-ci builderImage)
    • 209395b7c356 feat(dashboard): panes read /pipeapi/panes — retire the poller TSV projections
    Downloads
  • v0.1.62 06c884eb6f

    v0.1.62 Stable

    gitea_admin released this 2026-07-05 16:50:33 +00:00 | 2544 commits to trunk since this release

    Fixed

    • The page always fits the browser window again — and a section never exceeds one green
      screen.       v0.1.61's fixed 810px terminals were 24 dashboard rows (double a real terminal's
      line pitch), so three of them overflowed every window on load. Pane height is now
      min(equal share of the window, 480px) — 480px being one 80x24 IBM-i terminal window
      (24 lines × 20px terminal leading, ≈ sticky header + 13 rows) — with the chrome MEASURED
      from the DOM (body.offsetHeight minus the panes) rather than assumed, so the header/footer
      line-wrapping at green-screen widths is accounted for exactly. Verified fit=true by headless
      probe at 1280×800, 1440×1000, 1440×2400 (panes capped at 480px), and 660×640 with sections
      folded. The v0.1.61 invariant stands: opening a row fold never resizes a pane — fold content
      and the rows beneath it scroll inside the virtual terminal.

    Included changes (v0.1.61 -> v0.1.62)

    • a0cb3af2a01f fix(dashboard): page fits the window; a pane never exceeds one green screen
    Downloads
  • v0.1.61 9d2e175942

    v0.1.61 Stable

    gitea_admin released this 2026-07-05 16:23:43 +00:00 | 2549 commits to trunk since this release

    Changed

    • Panes are fixed 24-line IBM-i virtual terminals. Each of BUILDS / RELEASES / DEPLOYS is
      now a static 810px scroll box (5250 model-2 geometry: 1 sticky header line + 23 data rows at
      the 34px row pitch) — the viewport-adaptive row budget and the fold-open ~70vh growth are
      deleted (they pushed the page past the browser window when a fold opened). A row fold and
      the rows beneath it scroll inside the terminal; the pane never resizes. Full-history
      rendering (50 rows), keyboard scroll, sticky header, hover/open cross-highlight and the
      auto-reveal of highlighted build rows all unchanged.

    Included changes (v0.1.60 -> v0.1.61)

    • f562110ce662 feat(dashboard): panes are fixed 24-line IBM-i virtual terminals
    Downloads
  • v0.1.60 de053f2965

    v0.1.60 Stable

    gitea_admin released this 2026-07-05 15:57:43 +00:00 | 2554 commits to trunk since this release

    Changed

    • Panes scroll instead of cutting off history. The viewport-fit row budget now sets each
      pane's height, not its row count: BUILDS / RELEASES / DEPLOYS render the full retained
      history (50 rows, matching CR retention; release fetch limit follows) inside a scroll
      container with a sticky header — wheel/trackpad, or Tab/click to focus a pane and use
      arrows/PageUp/PageDown. A pane with an open row fold grows to ~70% of the window so
      galleries and logs breathe. Opening a release fold auto-scrolls BUILDS to the first
      cross-highlighted commit, so "the other commit in this release" is never out of reach.

    Included changes (v0.1.59 -> v0.1.60)

    • c16fb99eafed feat(dashboard): panes scroll the full history instead of cutting it off
    • 9c9d309b52d7 spec(deploy): model-check the kernel fleet roll; retire the drifted release specs
    Downloads
  • v0.1.59 797d2a55b3

    v0.1.59 Stable

    gitea_admin released this 2026-07-05 15:42:52 +00:00 | 2561 commits to trunk since this release

    Changed

    • Trace/status now delegate to the query service — the client-side join is deleted (Phase B). The
      dashboard SPA and pipectl each carried their own copy of the Build→Release→Deploy join (JS in
      dashboard.html, inline python in bin/pipectl), plus a duplicated Forgejo compare "first release
      containing" walk. Both now call the ONE server-side join in the pipelines query service (embedded in
      pipelines-operator): the SPA via a new same-origin /pipeapi/ nginx proxy (mirrors /relapi/,
      GET-only, in-cluster plain-HTTP to pipelines-operator-query...svc:9090), pipectl via the apiserver
      service-proxy (RBAC-gated by the existing kubeconfig — no Forgejo reachability or CA trust needed from
      the laptop). Deleted traceMatch/resolveTraceSha/traceContaining (SPA) and the inline python
      join + trace_version_sha (pipectl); the SPA keeps a pure traceHtml renderer, pipectl keeps only
      local file:line→sha git blame (the server has no working tree). Payoff: cross-project trace —
      a deploy's carrierSha is now followed into the seanfarm carrier commit and rendered as a carrier
      leg, the capability no single-project client could do. tests/dashboard-change-trace.test.js
      rewritten to exercise the renderer + assert the /pipeapi/ wiring.

    Included changes (v0.1.58 -> v0.1.59)

    • cebfedbb517d Merge remote-tracking branch 'origin/trunk' into feat/phase-b-query-service-repoint
    • cb34a53f1246 feat(dashboard,pipectl): repoint trace/status to the query service (Phase B)
    Downloads