Skip to content

Release 0.2.1 - #45

Merged
sodre merged 1 commit into
mainfrom
release/v0.2.1
Nov 21, 2026
Merged

sodre merged 1 commit into
mainfrom
release/v0.2.1

Conversation

@sodre

@sodre sodre commented Nov 21, 2026

Copy link
Copy Markdown
Member

Why

Since v0.2.0, main has gained the filter sandbox for hosts without namespaces (#34, #26, #30), the fix for clients whose clock runs behind (#36), and the Broker's grant expiry, approved certificate and approvals/current lookup (#39). Each addition is opt-in or a new response field, so no existing Integrator or operator setup changes on install.

What changed

Every version source moves from 0.2.0 to 0.2.1, as in #17:

  • Cargo.toml: the workspace version and the exact =0.2.1 pins on countersign-pki and countersign-protocol
  • Cargo.lock: only the five workspace crates change
  • packages/widget/package.json and packages/companion/package.json: the Companion version is what publish_desktop.py checks against the tag
  • recipe/recipe.yaml

Before the tag: the npm desktop publish

v0.2.0's npm-desktop job failed with ENEEDAUTH (run 44294196188), so the seven desktop packages are still at 0.1.1 on npm. The bootstrap token NPM_BOOTSTRAP_TOKEN is gone (the job's NODE_AUTH_TOKEN is empty), and only @zeroae/countersign-widget has a trusted publisher: it published 0.2.0 by OIDC from publish.yml. The seven desktop packages were last published by hand-held token at 0.1.1, and have no trusted publisher for distribution.yml. Before tagging, add one on npmjs.com to each of @zeroae/countersign and @zeroae/countersign-{linux,darwin,win32}-{x64,arm64}: owner zeroae, repository countersign, workflow distribution.yml, environment npm (docs/develop.md, "Switch to trusted publishing").

After merge

Tag the squash commit on main as v0.2.1 and push the tag. That starts the registry, distribution and handbook workflows.

Verification

  • python3 scripts/registry_release.py check --tag v0.2.1 passes.
  • cargo metadata --locked accepts the refreshed lockfile.
  • pnpm-lock.yaml holds no workspace package versions, so it needs no change. CI's pnpm install --frozen-lockfile confirms it.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sodre
sodre merged commit 7199c78 into main Nov 21, 2026
36 checks passed
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