Skip to content

capsulectl v0.1.0-rc23

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 26 Oct 15:56
· 140 commits to main since this release
8214f4b

capsulectl v0.1.0-rc23, a pre-release, tagged at 8214f4be2c08b1ccb534724b6a285ca22f8bda49. The full list of changes is in the CHANGELOG.

Coming from rc16 or older? Read rc17's "Before you upgrade" first: rc17's upgrade cannot be undone, and going straight to rc23 includes it.

Before you upgrade: the plugins ship from their own releases

This release carries only the capsulectl core. The book and deal plugins and the deal skill now build and release from their own repositories, each built against this release (#326):

  • capsulectl-book capsulectl/v0.1.0-rc23: evidencebook;
  • capsulectl-deal v0.1.0-rc23 and the deal skill (deal-skill-v0.1.0-rc23.tar.gz): evidencebook-deal.

Each plugin release takes the version of the capsulectl release it is built against.

capsulectl plugin install book|deal no longer downloads anything. Download the plugin file built for this release, check it against that release's SHA256SUMS and attestation, then install the file: capsulectl plugin install ./capsulectl-book-<version>-<os>-<arch> or ./capsulectl-deal-<version>-<os>-<arch>. Upgrading only the core leaves an installed plugin built for rc22, which the dispatch warning and doctor --install-check report until you install the matching plugin. If a plugin's release is not out yet, keep your rc22 plugin; it runs, with the version warning. Profiles, deal stores and books from rc22 are read unchanged: no format changes.

Breaking

  • Install by name is gone (#447). capsulectl plugin install book|deal refuses and gives the file form, as above. The hidden --release-url flag is gone, and this release has no plugin-<name> assets.
  • internal/cli is the public cli package (#444). Code that builds against github.com/action-state-group/capsule-cli/internal/cli moves to .../cli (and .../settlement). A build that sets -X .../internal/cli.CLIVersion must use the new path: -X silently ignores a symbol that does not exist.
  • verify --bundle is AAC's strict verifier for signatures, the checkpoint and witness receipts (#439, #440, #441). Bundles capsulectl and AAC write are unaffected. Some malformed bundles change verdict: a record whose signature and key_id are both null is now an invalid signature (INVALID, was INCOMPLETE); a checkpoint whose JSON copy has no log_id is now INVALID (was VALID); a receipt_b64 wrapped across lines or with non-zero trailing bits now fails (INVALID where it was withheld). The CHANGELOG lists each case.

Changed

  • The deal page compares builds by name (#448). On a page from a capsulectl-deal release, a step sealed by capsulectl before the move is marked as an earlier build, not an older version, and the note links the plugin's own release notes. Pages without the new data read as before.
  • The plugin handshake carries core_version (#444): the capsulectl release a first-party plugin embeds. Install, the dispatch warning and doctor --install-check compare it, falling back to version for older plugins. Mismatch messages name the release the plugin is built for.
  • Report pages take capsule-viewer at 4b08aad (#435, capsule-viewer#77). A bundle that did not verify gets the "Check failed" callout, the checks that failed and each record's id and status, with no record content. A capsule id listed more than once has one entry, with a note of how many times.
  • Dependencies: agent-action-capsule/go v0.13.1 (#441); capsule-viewer 4b08aad with agent-action-capsule ts 0.6.1 (#435).
  • CI (#447, #449): no plugin jobs; any path into the trees that moved out fails the build; the tests are sharded by measured time across eight race jobs.

Fixes

  • The capsulectl skill's scripted demo passes again (#447). It runs on a sqlite profile with the core verbs, including result build; it needed the book plugin since #236.

Known issues

  • Witness delivery text (#397). The pending text says the delivery is retried "at every tick". It is retried on the delivery backoff, up to an hour apart.
  • The deal known issues from rc22 (#415, #384, #422, #426) now belong to capsulectl-deal and are listed in its CHANGELOG.

Verify

In an empty directory:

V=v0.1.0-rc23; R=action-state-group/capsule-cli
gh release download "$V" --repo "$R"
shasum -a 256 -c SHA256SUMS
for f in capsulectl-"$V"-*-*; do
  gh attestation verify "$f" --bundle "capsulectl-$V.sigstore.json" --repo "$R" \
    --signer-workflow "$R/.github/workflows/release.yml"
done

--bundle needs no GitHub account. The loop checks the core binaries. Each plugin has its own repository, tag, file names and signer workflow, and its release notes give its verify command; don't adapt this loop for a plugin.

Once the install page, actionstate.ai/install, names this release, it publishes the SHA-256 of the linux/amd64 binary and of the attestation bundle. Those values do not come from the release itself.