Skip to content

chore(release): sdk 0.11.0, cli 0.6.0, python 0.11.0 — offline V3 mandate verify#115

Merged
fabianocruz merged 5 commits into
mainfrom
chore/release-v3-verify
Jul 5, 2026
Merged

chore(release): sdk 0.11.0, cli 0.6.0, python 0.11.0 — offline V3 mandate verify#115
fabianocruz merged 5 commits into
mainfrom
chore/release-v3-verify

Conversation

@fabianocruz

Copy link
Copy Markdown
Member

Version bumps + changelogs for the #114 surface (already merged): @codespar/sdk/mandate subpath, codespar mandate verify, codespar.mandate Python submodule with the [verify] extra.

Release plan after merge:

  1. Tag v0.11.0 on the merge commit → publish.yml (npm OIDC trusted publishing) ships sdk 0.11.0 + cli 0.6.0; every other package soft-passes at its already-published version.
  2. gh release create python-v0.11.0publish-python.yml (PyPI trusted publishing) ships codespar 0.11.0.

🤖 Generated with Claude Code

fabianocruz and others added 5 commits July 5, 2026 13:22
…date verify

Version bumps + changelogs for the #114 surface: @codespar/sdk/mandate
subpath, codespar mandate verify command, codespar.mandate Python
submodule with the [verify] extra. Publish via the v* tag (npm OIDC)
and the python-v* release (PyPI trusted publishing).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ks, not tarballs

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ed registry install

The stale ^0.10.1 range stopped matching the workspace's 0.11.0, so npm
nested a 0.10.11 tarball under packages/cli and the lock drift check
(correctly) refused it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@codespar/mcp's ^0.10.1 runtime dep stopped resolving against the
workspace's 0.11.0 (CI typecheck could not find the module), and every
adapter's ^0.10.0 peer would ERESOLVE for consumers pairing it with sdk
0.11.0. Ranges widen to '|| ^0.11.0' and each touched package takes a
patch bump so the corrected manifests actually ship: adapters 0.4.1,
mcp 0.5.3.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…rollup optionals

The from-scratch regen on macOS dropped @rollup/rollup-linux-x64-gnu
(npm/cli#4828), so CI's vitest died before running a single test.
Incremental install over main's lock keeps every platform variant;
nested @codespar/* installs stay at zero now that the ranges match.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@fabianocruz fabianocruz merged commit 0c0aacd into main Jul 5, 2026
10 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