inkscape_mcp: Skill for Claude Code

Cutting an inkscape-mcp release

A release is: bump version → commit → tag vX.Y.Z → push main + tag → the Release workflow auto-creates the GitHub release → manually dispatch the Publish workflow to push to PyPI. Confirm the target version with the user before starting if it isn't given.

1. Prerequisites

git checkout main && git pull --ff-only
git status --short          # working tree should be clean (stash unrelated changes)
grep -n 'version = ' pyproject.toml      # current version, two lines

2. Pre-release checks — lint, tests, security

The tag triggers the CI + Security workflows; a release must not ship red. Run these locally first and fix everything before bumping the version.

uv run ruff format --check .    # formatting — run `uv run ruff format .` to fix
uv run ruff check .             # lint
uv run pytest -q                # tests

Security — audit third-party deps (mirrors what the Security workflow runs):

uv export --no-emit-project --format requirements-txt -o /tmp/req.txt
uv run --with pip-audit pip-audit -r /tmp/req.txt --disable-pip --strict

If pip-audit flags anything, bump the affected package(s) to a fixed (ideally the latest) version and re-audit until it reports "No known vulnerabilities found":

uv lock --upgrade-package <pkg>        # one --upgrade-package per package
# then re-export + re-audit (above) to confirm clean

Transitive deps (e.g. joserfc, pydantic-settings) often have no Dependabot PR — bump them here manually. Commit any format/lint and uv.lock fixes (as their own commit) so main is green before you tag.

3. Bump the version

The version string lives in exactly three release-relevant locations. Set all three to the new X.Y.Z:

• pyproject.toml — [project] version (~line 7)
• pyproject.toml — [tool.fastmcp] version (~line 118)
• src/inkscape_mcp/__init__.py — __version__

Do not touch src/inkscape_mcp/transport.py — its version="1.0.0" is a docstring example, not the real version.