Skip to content

Release 0.2.0 - #17

Merged
sodre merged 1 commit into
mainfrom
release/v0.2.0
Nov 18, 2026
Merged

sodre merged 1 commit into
mainfrom
release/v0.2.0

Conversation

@sodre

@sodre sodre commented Nov 18, 2026

Copy link
Copy Markdown
Member

Why

The widget's redesigned default look and the Companion's per-Integrator theming (#11, #13) are new features since v0.1.1. Both npm's ^0.1.1 and Cargo's 0.1.1 accept any 0.1.x, so a patch release would change every Integrator's page on their next routine install. A minor bump lets them opt in.

What changed

Every version source moves from 0.1.1 to 0.2.0:

  • Cargo.toml: the workspace version and the exact =0.2.0 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

The five crates have no source changes since v0.1.1. They republish because every package shares one version.

After merge

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

Verification

  • python3 scripts/registry_release.py check --tag v0.2.0 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

Bump the Rust workspace, the widget, the Companion and the conda recipe
to 0.2.0, with the exact internal crate pins and Cargo.lock to match.
The widget's redesigned default look and the Companion's per-Integrator
theming are new features, so this is a minor release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sodre
sodre merged commit 758d05d into main Nov 18, 2026
30 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