sean/pipelines
Watch
1
0
Fork
You've already forked pipelines
 0
Code Issues Pull requests 12 Projects Releases 291 Packages Wiki Activity
291 releases 291 tags
  • v0.1.101 ecb504c691

    v0.1.101 Stable

    pipeline-bot released this 2026-07-08 13:03:49 +00:00 | 829 commits to main since this release

    Changed

    • Log-fold window tuned 200 -> 60. 200 (attempted "all retained builds") made the poller's durable
      fallback do ~3600 per-workflow MinIO listings per cycle and crawl; 60 covers the visible pane +
      scroll while keeping the poller responsive. (Unbounded log coverage needs a single recursive
      listing or a persistent /shared cache — follow-up.)

    Included changes (v0.1.100 -> v0.1.101)

    • 37386948c3d8 fix(dashboard): log window 200->60 (per-wf mc-ls cost crawled the poller)
    Downloads
  • v0.1.100 73120f0f35

    v0.1.100 Stable

    pipeline-bot released this 2026-07-08 12:54:42 +00:00 | 834 commits to main since this release

    Changed

    • Build folds now show BOTH artifacts and logs for recent builds. The download-mirror window is
      sorted by build time (.status.finishedAt) instead of CR-creation time, so backfilled CRs
      (created at backfill time) no longer push genuinely-recent commits out of the newest-24 window.
    • Build/deploy logs now appear in every retained build's dropdown: the poller log window widened
      40 → 200 (the operator's build-retention). Logs are tiny text and the poller already resolves a
      GC'd workflow's logs from the immutable MinIO archive, so this is ~tens of MB (the download
      mirror stays disk-bound at 24).

    Included changes (v0.1.99 -> v0.1.100)

    • 78ffaa0181aa feat(dashboard): logs in every dropdown + time-sorted download window
    Downloads
  • v0.1.99 2987f62ace

    v0.1.99 Stable

    pipeline-bot released this 2026-07-08 12:26:22 +00:00 | 840 commits to main since this release

    Changed

    • Incremental release.

    Included changes (v0.1.98 -> v0.1.99)

    • 6a880969d0bc fix(dashboard): revert build-dl window 40->24 (node-root DiskPressure)
    Downloads
  • v0.1.98 01b579e9a7

    v0.1.98 Stable

    pipeline-bot released this 2026-07-08 12:16:53 +00:00 | 845 commits to main since this release

    Changed

    • Dashboard folds now support a per-project artifact keep-list (FLAGS[proj].artifacts): when set,
      only matching download chips render in BOTH the build fold and the release fold; reels (.mp4)
      always show. zelnet declares [/\.exe$/i, /macos/i] so its folds surface only the testable
      Windows + macOS builds, hiding the Linux tarballs, rpm/deb, checksums, and screenshot posters.
      Other projects are unaffected (unset ⇒ keep all). New artifactKeep(name) + test.
    • Build-download mirror window aligned 24 → 40 (the log/trace windows) so every build the BUILDS
      pane folds open via its logs also has its Windows/Mac binaries downloadable — no more "logs but
      no downloads" rows for builds older than the 24-deep window.

    Included changes (v0.1.97 -> v0.1.98)

    • bd74654c67f8 feat(dashboard): per-project artifact keep-list (zelnet = Win+Mac+reels)
    Downloads
  • v0.1.97 82ffd89453

    v0.1.97 Stable

    pipeline-bot released this 2026-07-08 11:46:40 +00:00 | 850 commits to main since this release

    Changed

    • Dashboard BUILDS pane is now operational, not a ledger: a build row renders only when it can
      fold open to something (live logs, flame trace, dev binaries, or archived step logs) or is still
      in flight. Terminal builds whose fold sources aged out — and backfilled Change records with no
      workflow — no longer appear as dropdown-less dead rows; they survive as data behind the release
      change-list. New one-line buildPaneVisible(w,fd) policy + tests/dashboard-build-pane.test.js.

    Included changes (v0.1.96 -> v0.1.97)

    • 0d3addaa3127 fix(dashboard): hide foldless builds — BUILDS pane is operational, not a ledger
    Downloads
  • v0.1.96 c7f2ee4da1

    v0.1.96 Stable

    pipeline-bot released this 2026-07-08 10:51:33 +00:00 | 856 commits to main since this release

    Changed

    • Incremental release.

    Included changes (v0.1.95 -> v0.1.96)

    • 900492027902 fix(backfill): renders.tar.gz probe uses mc stat — mc ls prefix semantics pruned real history
    Downloads
  • v0.1.95 b76e5cff7b

    v0.1.95 Stable

    pipeline-bot released this 2026-07-08 10:36:26 +00:00 | 862 commits to main since this release

    Fixed

    • RELEASES pane shows only releases — the declared ship path (pipectl / shipd / the
      cadence CronJob) creates a PipelineRelease CR per "ship?" decision, and the pane rendered them
      all: phase=Skipped "—" rows piled up 4/day per declared-cadence project, versionless Succeeded
      intent shells lingered from ship-mashing, and a version shipped through both paths (projected
      -release- CR + declared -ship- CR) rendered twice. Two one-line SPA helpers fix it:
      isShipIntent drops Skipped and versionless+tagless terminal non-failures (Running/Pending ships
      and Failed/Error releases stay loud), and dedupReleaseRows renders each version once, keeping
      the richest row (workflow > tag > Succeeded). Filtering runs BEFORE the Forgejo-synth merge so a
      dropped junk row lets the durable tag-derived row re-appear. Covered by
      tests/dashboard-release-rows.test.js (also run by the in-cluster CI guard).
    • BUILDS pane shows only commits a build pipeline actually built — the gitops validate
      (pipeline-validate / pipeline-validate-flux) writes a builds/<short>/MANIFEST for every
      render, including the trunk re-validation that runs as deploy prep. pipeline-build-backfill
      turned those into BUILD rows, so un-openable plumbing commits (devbump / release-merge /
      land-merge) littered the pane with no logs or artifacts behind them. The validate now stamps an
      explicit kind= in the MANIFEST (build on a feature branch — the change's CI test; staging
      on the trunk — deploy prep), and the backfill's new classify_build_record keeps only real
      builds. Legacy records with no kind fall back to the render's signature artifact
      (renders.tar.gz on the trunk), so a build's genuine compile output is never misread. Phantom
      build CRs created before this fix are pruned on the backfill's next hourly run (delete guarded to
      backfilled=true — a projector-owned live build is never touched). This replaces the last
      reliance on the overloaded mode= field for the build/render distinction. Covered by
      tests/backfill-classify.test.js.

    Included changes (v0.1.94 -> v0.1.95)

    • 1ef614bacdd3 fix(dashboard): RELEASES pane shows only releases — drop ship-intents, dedup versions
    • fc3117b156ff test(backfill): run classify guard in-cluster CI; POSIX-sh portable
    • 8ae6d4d1fda6 fix(backfill): BUILDS pane shows only commits a build pipeline built
    Downloads
  • v0.1.94 0786e9721b

    v0.1.94 Stable

    pipeline-bot released this 2026-07-07 10:57:54 +00:00 | 870 commits to main since this release

    Added

    • builder-images builds pull packages through pkg-cache — pipeline-build-images's
      shared build-one leg now passes --opt build-arg:PKG_CACHE=http://pkg-cache.pkg-cache.svc.cluster.local:8080,
      so every dockerfile-set image whose Containerfile declares ARG PKG_CACHE fetches
      apt/dnf/apk + nix + stable raw binaries from the in-cluster pull-through cache instead
      of the internet. buildkit ignores the build-arg for images that don't declare it (warning
      only), so this is safe for all images.

    Included changes (v0.1.93 -> v0.1.94)

    • c5429c8a2320 feat(pkg-cache): builder-images builds fetch packages through pkg-cache
    • 7f349a10c461 feat(dashboard): deploy row shows '→ target', versions move to the fold
    Downloads
  • v0.1.93 d3aa57088c

    v0.1.93 Stable

    pipeline-bot released this 2026-07-07 06:55:21 +00:00 | 877 commits to main since this release

    Fixed

    • pipeline-staging declares the codeberg volume so the promote step's skopeo-push
      (reached via templateRef into pipeline-promote-image) can mount codeberg-push-secret.
      A templateRef'd template does NOT inherit its own WorkflowTemplate's workflow-level volumes,
      so the codeberg-push added to pipeline-promote-image broke EVERY operator release at
      promote[0].push with volume 'codeberg' not found in workflow spec — mirrors how
      forgejo/docker are already declared here. First operator release after the codeberg-push
      landed surfaced it.

    Included changes (v0.1.92 -> v0.1.93)

    • 718bf441d8fb fix(pipeline-staging): declare codeberg volume for skopeo-push
    Downloads
  • v0.1.92 c2071fd4ef

    v0.1.92 Stable

    pipeline-bot released this 2026-07-06 23:42:24 +00:00 | 882 commits to main since this release

    Changed

    • De-admin (data-plane, pass 2): the kernel + builder-images build/promote legs
      (pipeline-build-kernel, pipeline-build-images, pipeline-promote-images,
      pipeline-promote-kernel) now mount forgejo-pipeline-bot-token instead of
      forgejo-admin-token — same clone/API-read + branch/PR/merge/tag/release ops, all
      within the bot's write:repository + write-collaborator access. Only the provisioner
      webhook (needs repo-admin) and forgejo-sync (direct-push-to-main) still use the admin
      token; those need the Phase E rework (ForgejoWebhook CR + ff-merge restructure).

    Included changes (v0.1.91 -> v0.1.92)

    • 0a5fdb0f1bd6 feat(de-admin): kernel + builder-images legs run as pipeline-bot (pass 2)
    Downloads