th-server-12211: require published core 0.16.1 + bump to 1.22.11#221
Merged
Conversation
… bump to 1.22.11 Server 1.22.10 called with_model_ceiling but required core ^0.16; crates.io topped out at core 0.16.0 (predates the method), so external cargo builds resolved 0.16.0 and failed to compile. Core 0.16.1 is now published with the API — pin the workspace core dep to a plain registry "0.16.1" (dropping the stopgap git/rev = d03fa10 pin) so the published server/facade require ^0.16.1 and resolve the fixed engine. Lockstep bump all artifacts 1.22.10 -> 1.22.11. Co-Authored-By: Claude Opus 4.8 <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
1 participant
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.
Problem
smooai-smooth-operator-server1.22.10 (and facade 1.22.10) callwith_model_ceilingbut their published manifests required core^0.16. crates.io topped out at core 0.16.0, which predates that method — so any externalcargo buildagainst the published server resolved 0.16.0 and failed to compile. The workspace built internally only because the core dep was a stopgapgit/rev = d03fa10pin (the unpublished 0.16.1 content).Fix
with_model_ceiling.smooai-smooth-operator-core = "0.16.1"(drops the stopgap git pin; restores the documented "published crate is the single source" model). Published server/facade now require^0.16.1, so the broken 0.16.0 can no longer be resolved.Verification
cargo check --workspace --lockedbuilds against published core 0.16.1.cargo publish --dry-run --locked -p smooai-smooth-operatorpackages clean; packaged manifest declaressmooai-smooth-operator-core version = "0.16.1".cargo add smooai-smooth-operator-server@1.22.11 && cargo checkagainst published-only crates) runs after the release workflow publishes 1.22.11.🤖 Generated with Claude Code