Skip to content

feat: add release-beta/stable pipeline (deno + workflows) - #6

Merged
PerishCode merged 1 commit into
mainfrom
feat/release-pipeline
Jun 29, 2026
Merged

PerishCode merged 1 commit into
mainfrom
feat/release-pipeline

Conversation

@PerishCode

Copy link
Copy Markdown
Owner

No description provided.

Ports flavor's release design to the runseal + Deno system. The workflows own
the job DAG + cross-platform build matrix; per-step logic lives in Deno under
.runseal/lib/release/ and is invoked as `runseal :release <step>` (CI calls the
same wrapper via `deno run`, so no runseal bootstrap is needed cross-platform).

- meta: remote <channel>/latest/metadata.json is the version source of truth;
  strict monotonic resolution with defensive R2 reads (403≠missing, 404 double
  check). Version source is the workspace Cargo.toml.
- r2/artifacts/publish/verify: aws-CLI uploads, sha256 checksums, archive member
  checks, metadata.json, re-fetch + HEAD verification. Single `santi` artifact
  per target; managers published every release so installs work on any channel.
- smoke: strict — install from the public URL via manage.*, then `santi --help`
  and a live `santi service` /health, then uninstall (Deno, cross-platform).
- manage.sh / manage.ps1: end-user distribution installers (not wrappers).
- santi gains `--version` (needed by the installers).
- verify job runs `runseal :guard` so release verification matches local.
@PerishCode
PerishCode merged commit 8c16ed4 into main Jun 29, 2026
3 checks passed
@PerishCode
PerishCode deleted the feat/release-pipeline branch June 29, 2026 09:33
PerishCode pushed a commit that referenced this pull request Aug 1, 2026
PerishCode pushed a commit that referenced this pull request Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant