chore(release): 0.4.1 — the bearer credential, where it can be installed from - #18
Merged
Conversation
…led from khwan-mcp installs khwan from PyPI, not from this repository, so merging #17 changed nothing it can reach: the MCP layer still cannot call `Khwan(bearer_token=…)` until a version carrying it is published. The same shape as the engine pin between khwan-api and khwan-worker that came up twice today — merged is not deployed, and the boundary is a package registry rather than a git ref. Additive and backwards compatible: `api_key` behaves exactly as before, and the existing 35 tests pass untouched.
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.
Version bump only,
0.4.0→0.4.1.khwan-mcpinstallskhwanfrom PyPI, not from this repository — so merging #17 changed nothing it can reach. The MCP layer cannot callKhwan(bearer_token=…)until a published version carries it.Same shape as the engine pin between
khwan-apiandkhwan-workerthat came up twice today: merged is not deployed. The boundary here is a package registry rather than a git ref, and it is just as invisible.Additive and backwards compatible.
api_keybehaves exactly as before; the existing 35 tests pass untouched, plus the 10 new ones.After merging, cutting
v0.4.1publishes to PyPI over Trusted Publishing, and then thestreamable_http_app()mount in khwan-mcp is unblocked — the last piece of Phase 1.