What problem does it solve? Cutting a ResoniteIO release requires keeping three version strings in lockstep, updating the changelog, pushing a tag, and coordinating a multi-job GitHub Actions pipeline that publishes the mod zip to GitHub Releases and the Python package to PyPI — a process with many failure points like version mismatches, stale renderer prebuilts, and broken changelog extraction. ## Core Features & Use Cases - Lockstep version bumping: Updates the csproj <Version>, pyproject.toml version, and CHANGELOG.md (including link reference definitions) together, then runs uv lock and the full just run verification suite. - Tag-driven publish pipeline: Pushing a v* tag triggers publish.yml, which runs version guards, renderer prebuilt drift checks, PackTS mod zip builds, PyPI Trusted Publishing via OIDC, and GitHub Release creation with changelog-extracted notes. - Prerelease and troubleshooting support: Covers alpha/beta/rc prerelease tagging, one-time PyPI Trusted Publisher setup, and diagnosis of common failures like version-guard mismatches and stale renderer prebuilts. - Use Case: You want to ship ResoniteIO v0.2.0 — the skill walks you through the bump branch, changelog edits, tag push, and post-release verification including Gale local mod import. ## Quick Start Ask the assistant to cut a new ResoniteIO release for version X.Y.Z and it will bump the versions, update the changelog, and guide the tag push that publishes to PyPI and GitHub Releases.
