Repository navigation
Release 0.2.1 - #15
Merged
Merged
Conversation
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.
Bumps the version to 0.2.1 in
pyproject.tomlandserver.json(top-level and package), as the release workflow requires.What's in 0.2.1 (since 0.2.0):
/searchreturns 502{"error": "SearXNG returned no results; failing engines: ..."}instead of an empty 200 when every engine is blocked (and a tool error over MCP); partial failures are logged by engine nameChecked:
mcp-publisher validatepasses for server.json, versions match what the release workflow's tag check expects (v0.2.1), 49 tests pass.After merge: tag
v0.2.1to publish to PyPI, ghcr.io, the MCP Registry and GitHub Releases.