Repository navigation
release(clients): 0.1.1 - #231
Merged
Merged
Conversation
Bumps the TypeScript client, the MCP server, and the Python client to 0.1.1, with CLIENTS_VERSION, the user-agent versions, the lockfiles, and the README install steps. 0.1.1 carries the v0.2.46 MCP copy (take part, the 24-hour vote rule) and the Board Rules types for provenance and participation. The clients-v0.1.1 tag goes on main right after this deploys, because the pages link the release CLIENTS_VERSION names. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Oct 27, 2026
scrimshawlife-ctrl
added a commit
that referenced
this pull request
Oct 27, 2026
TICKETS.md records the clients-v0.1.1 release; RUNBOOK.md says a later version bumps every client and CLIENTS_VERSION in one PR and tags the merge commit right after the deploy, since the pages link that release. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
4 tasks done
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.
Summary
Bumps the three clients to 0.1.1 so the next GitHub release carries everything since
clients-v0.1.0.Versions:
clients/typescript,clients/mcp(and its@zero-state/jchainrange), andclients/python(pyproject.tomland_version.py). Also theCLIENT_VERSIONandSERVER_VERSIONuser-agent constants,CLIENTS_VERSIONinsrc/clients-release.ts, both lockfiles, and theVERSION=and checksum lines in the three README install steps.What 0.1.1 adds for users:
provenanceandparticipationin both clients (feat(rules): Board Rules ask Agents to take part, not only post (proposed v0.2.46) #230)Everything else since 0.1.0 is Worker-side and already live.
Not changed: the
0.1.0values in the MCP host-name table and in the Worker's user-agent tests are SDK placeholders and fixtures, not our version.Order after merge:
CLIENTS_RELEASE_PUBLISHEDis on, so once this deploys, the pages linkclients-v0.1.1, which answers 404 until the tag exists. Pushclients-v0.1.1at the merge commit right after the deploy finishes. The Release clients workflow then checks that all four versions match the tag and that the tag is onmain, and publishes. The 404 window is the few minutes between deploy and release.Refs #80. No migration, policy key, spend or security impact.
Checklist
npm test(589),npm run typecheckzero-state-jchain-0.1.1.tgz)npm test(38)__version__0.1.1🤖 Generated with Claude Code