Repository navigation
chore(sdks): bump daemon-client packages for antd 0.16.0 - #386
Merged
Merged
Conversation
The pointer and manifest APIs (and the C# REST ALREADY_EXISTS mapping, the MCP SERVICE_UNAVAILABLE hint and the Swift stream error code) are on main but in no published package yet. Bump every registry-published daemon client so each publish workflow's tag-equals-manifest check passes: - antd-py (PyPI antd): pyproject 0.3.0 - antd-js (npm @withautonomi/antd): package.json and package-lock 0.3.0 - antd-csharp (NuGet Autonomi.Antd): csproj <Version> 0.3.0. REST ALREADY_EXISTS now throws AlreadyExistsException (README "Upgrading") - antd-dart (pub.dev antd_client): pubspec 0.3.0; CHANGELOG "Unreleased" becomes 0.3.0; README dependency ^0.3.0 - antd-ruby (RubyGems antd): VERSION 0.3.0 - antd-rust (crates.io antd-client, not yet published): Cargo.toml and Cargo.lock 0.4.0, README "0.4". The new AntdError variants are breaking (README "Upgrading from 0.3.x"); 0.3.0 was bumped in #324 but never published. antd-mcp stays 0.1.0 (never published) and now requires antd[rest]>=0.3.0,<0.4, the first SDK with the pointer and manifest APIs its tools call. The import guards in server.py, manifests.py and errors.py stay, for installs that bypass the floor; comments and the README now name 0.3.0. PHP (Packagist, via the mirror) takes its version from the php-v tag only. antd-go was released by the v0.16.0 tag (antd-go/v0.16.0). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…PyPI The security audit resolves each pyproject against PyPI, and antd 0.3.0 isn't published yet, so a >=0.3.0 floor can't resolve. antd-mcp is not published either; its floor moves to 0.3.0 in a follow-up once the antd-py-v0.3.0 tag has published. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Python CI installs the checkout's antd-py (now 0.3.0) with antd-mcp, so the <0.3 cap no longer resolves. The security audit resolves against PyPI, where only 0.2.0 exists, so the floor can't move to 0.3.0 yet. >=0.2.0,<0.4 satisfies both; the pointer and manifest tools already register only when the installed SDK has them. The floor moves to 0.3.0 once 0.3.0 is on PyPI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 22, 2026
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.
Package bump for the antd 0.16.0 round, following the pattern of #311. The pointer and manifest APIs are on main but in no published package yet, so every registry-published daemon client moves up a minor version.
antdantd-py-v0.3.0@withautonomi/antdantd-js-v0.3.0Autonomi.Antdnuget-v0.3.0antd_client^0.3.0)dart-v0.3.0antdruby-v0.3.0autonomi/antd(mirror)php-v0.3.0antd-client(held: no crates.io token yet)"0.4")antd-mcp(held, never published)antd[rest]>=0.2.0,<0.4(see below)Notes
ALREADY_EXISTSnow throwsAlreadyExistsException, where it used to throwForkException(fix(antd-csharp, antd-mcp, antd-swift): error-mapping gaps (V2-1575) #378).AntdErrorvariants ("Upgrading from 0.3.x"). 0.3.0 was bumped in chore(antd-rust): bump antd-client to 0.3.0 for antd 0.15.0 #324 but never published; antd-client has never been on crates.io, so 0.4.0 will be its first release there.antd[rest]>=0.2.0,<0.4. Only the cap moves; the floor stays at 0.2.0. The two CI paths disagree until antd 0.3.0 is on PyPI: Python CI installs the checkout's antd-py (0.3.0), which the old<0.3cap rejected (9b1f307), and the security audit resolves against PyPI, which has no 0.3.0 for a>=0.3.0floor (a561eb6). Checked locally: the CI install gives 123 passed, 2 skipped, anduv pip compileresolvesantd==0.2.0. The pointer and manifest tools register only when the installed SDK has them. Afterantd-py-v0.3.0publishes, a follow-up raises the floor to 0.3.0.v0.16.0tag (antd-go/v0.16.0).After merge
Push one tag per push (GitHub drops workflow events when more than 3 tags arrive in one push), in this order:
antd-py-v0.3.0,antd-js-v0.3.0,nuget-v0.3.0,dart-v0.3.0,ruby-v0.3.0,php-v0.3.0. Then approve each environment and check that each registry lists the new version.Verified
cargo metadata --lockedfor antd-rust.0.2.0mentions in these packages are history notes ("new in 0.2.0") and the MCP compat tests that simulate a 0.2.0 SDK.🤖 Generated with Claude Code