chore(release): v0.5.5 — security patch#29
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
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.
Summary
Patch release publicizing the transitive-dep CVE fixes from #28.
__version__to 0.5.5 insrc/ssh_mcp/__init__.py## [0.5.5] - 2026-05-02entry toCHANGELOG.mdWhat ships
uv.lock(already on main from chore(deps): consolidate dotenv/multipart bumps + suppress unfixable pip CVE #28).uv.lock(already on main from chore(deps): consolidate dotenv/multipart bumps + suppress unfixable pip CVE #28).--ignore-vuln CVE-2026-3219for the runner-bundled pip 26.0.1 (no upstream fix yet; auto-revisit scheduled for 2026-05-16).Test plan
uv run pytest -q— 520/520 passing locally0.5.5afteruv syncv0.5.5on main and push tag to trigger Docker image rebuild + tagged pushRisk
Zero — no source changes, only
__version__string + CHANGELOG entry. The actual security fixes already shipped via #28 and are running on the:latestDocker tag; this just makes the fix opt-in for users pinning to a tagged version.