Skip to content

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 30 Oct 07:41
· 259 commits to main since this release
v0.8.0
b8ea3b0

What's new in 0.8.0

Full list: CHANGELOG.md.

Breaking changes and operator actions on upgrade

  • RPP bindings: a binding that declares [scopes] is now the scope ceiling; token scopes cannot widen it, and allowed = [] grants nothing. Before upgrading, check that every binding with a [scopes] section lists each scope its holder uses (#209).
  • RPP handoff: an explicit scopes = [] is preserved as [scopes] allowed = []. Omitted scopes keep the defaults and now log a warning.
  • Collapsed molecules are terminal: cs stuck and cs evolve refuse a molecule in a terminal status instead of moving it out of it.
  • API: POST /v1/molecules no longer returns the adapter's local molecule_dir.

Highlights

  • Remote parity: evolve, resurrect, prime, deps, decay, merge and transform are HTTP routes with matching cosmon-remote molecule subcommands, each calling the same operation as its cs verb.
  • Remote read surface: GET /v1/ledger (SSE with resume cursor), paged and ETag-aware GET /v1/molecules, and an observer handoff preset.
  • Conditional, idempotent cs collapse (--key, --expect-status, --expect-revision) with cs collapse-receipt.
  • Worker hosts: [transport] backend = "tmux" | "herdr", durable exit receipts for Codex exec workers, and cs terminal.
  • Sessions: cs sessions gains launch, seats, lifecycle, checkpoint stage and hook install.
  • cs fleet resolve carries the agent adapter key and refuses unknown keys under --strict.
  • Performance: cs run and cs wait no longer re-parse the journal on every tick.
  • Security: pulldown-cmark 0.13.5 (RUSTSEC-2026-0414), tokio 1.51.6 (RUSTSEC-2026-0386), plus rustls / quinn-proto / webpki updates.

Signed release

Every binary attached below is reproducibly built (cargo build --release --locked, SOURCE_DATE_EPOCH pinned), cosign-signed (keyless, Sigstore),
and anchored in the public Rekor transparency log. An SPDX SBOM is attached
per target.

Install

All three routes below deliver the same signed bytes — the tarballs
attached to this release. They cover macOS and Linux alike, on arm64 and
x86_64 (Linux builds are statically linked against musl, so no glibc version
to match).

Native install script (recommended, macOS + Linux):

curl -fsSL https://noogram.org/cosmon/install.sh | sh
cs --version

It detects your platform, downloads the matching tarball, and fails closed
if the sha256 does not match the published SHA256SUMS.

The installer itself is attached below as cosmon-install-<version>.sh, signed
and Rekor-anchored like the binaries. Piping it into sh consumes it before
that signature can be checked, so if you want the signature to actually do work
— shared machine, CI, first install — take the verify-then-run form instead:

ver=<version>          # the release version, without the leading v
base="https://github.com/noogram/cosmon/releases/download/v${ver}"
curl -fsSLO "${base}/cosmon-install-${ver}.sh"
curl -fsSLO "${base}/cosmon-install-${ver}.sh.sig"
curl -fsSLO "${base}/cosmon-install-${ver}.sh.pem"

cosign verify-blob \
  --certificate-identity-regexp 'https://github.com/.*/cosmon/.github/workflows/release.yml@.*' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --signature  "cosmon-install-${ver}.sh.sig" \
  --certificate "cosmon-install-${ver}.sh.pem" \
  "cosmon-install-${ver}.sh" \
  && sh "cosmon-install-${ver}.sh"

The && is load-bearing: cosign verify-blob exits non-zero on anything it
cannot tie back to release.yml at a cosmon tag, and that exit status is what
stops the script from running.

Homebrew (macOS + Linuxbrew):

brew install noogram/tap/cosmon
cs --version

The tap formula points at these very tarballs; brew checks the same digests.

From source (any platform with a Rust toolchain, MSRV 1.88):

cargo install --git https://github.com/noogram/cosmon.git --locked cosmon-cli

This compiles locally, so it produces your binary rather than the signed one
attached here — the verification steps below apply to the first two routes.

Verify the binary you installed

cosign verify-blob \
  --certificate-identity-regexp 'https://github.com/.*/cosmon/.github/workflows/release.yml@.*' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  --signature  cosmon-<version>-<target>.sig \
  --certificate cosmon-<version>-<target>.pem \
  "$(which cs)"
# exits 0 on a green signature

Self-host the remote service

Each target also ships a cosmon-service-<version>-<target>.tar.gz bundle
containing the cosmon-rpp-adapter (HTTP fente) and cs-oidc-mock (demo IdP)
binaries — signed and Rekor-anchored like the cs tarball. The
Run cosmon as a remote service
how-to deploys directly from this bundle; no Rust toolchain required.

Full operator instructions:
docs/guides/release-verification.md.


Full Changelog: v0.7.3...v0.8.0