Repository navigation
chore(release): 3.0.1 — first PyPI release - #18
Merged
Merged
Conversation
First release to be published on PyPI. Bumps version in pyproject.toml and server.json, promotes the Unreleased CHANGELOG section to 3.0.1, and regenerates sbom.json so its root component version matches the tag. 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
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.
Release prep for 3.0.1, the first version to be published to PyPI (
pip install metasploit-mcp).Changes
3.0.1inpyproject.tomlandserver.json(both fields).[Unreleased]CHANGELOG section to[3.0.1](security fixes: CVE-2026-5463 mitigation +mcpbump; CI hardening; unofficial/Rapid7 disclaimers).sbom.jsonso its root component version is3.0.1.Why 3.0.1 (not 3.0.0)
v3.0.0is already git-tagged and its code predates the security fixes merged in #17. Releasing a fresh3.0.1keeps the PyPI artifact consistent with the tagged commit.Release trigger (after merge)
Tag
v3.0.1onmain→release.ymlruns: verify tag==version, SBOM freshness, build,twine check, PyPI publish (OIDC Trusted Publishing), and GitHub Release withsbom.jsonattached.Precondition: PyPI Trusted Publisher must be registered for
setuidloot/MetasploitMCP(workflowrelease.yml, envpypi).Verified locally
poetry build,twine check(PASSED), andgenerate_sbom.py --checkall pass for 3.0.1.🤖 Generated with Claude Code