Repository navigation
Release 0.2.1 - #45
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Since v0.2.0,
mainhas 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 andapprovals/currentlookup (#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.1pins oncountersign-pkiandcountersign-protocolCargo.lock: only the five workspace crates changepackages/widget/package.jsonandpackages/companion/package.json: the Companion version is whatpublish_desktop.pychecks against the tagrecipe/recipe.yamlBefore the tag: the npm desktop publish
v0.2.0's
npm-desktopjob failed withENEEDAUTH(run 44294196188), so the seven desktop packages are still at 0.1.1 on npm. The bootstrap tokenNPM_BOOTSTRAP_TOKENis gone (the job'sNODE_AUTH_TOKENis empty), and only@zeroae/countersign-widgethas a trusted publisher: it published 0.2.0 by OIDC frompublish.yml. The seven desktop packages were last published by hand-held token at 0.1.1, and have no trusted publisher fordistribution.yml. Before tagging, add one on npmjs.com to each of@zeroae/countersignand@zeroae/countersign-{linux,darwin,win32}-{x64,arm64}: ownerzeroae, repositorycountersign, workflowdistribution.yml, environmentnpm(docs/develop.md, "Switch to trusted publishing").After merge
Tag the squash commit on
mainasv0.2.1and push the tag. That starts the registry, distribution and handbook workflows.Verification
python3 scripts/registry_release.py check --tag v0.2.1passes.cargo metadata --lockedaccepts the refreshed lockfile.pnpm-lock.yamlholds no workspace package versions, so it needs no change. CI'spnpm install --frozen-lockfileconfirms it.🤖 Generated with Claude Code