What problem does it solve?
Cutting a dbt-materialize release is a mechanical but error-prone chore: two version strings must stay in sync, the CHANGELOG must be dated correctly, and the release PR must follow a strict branch/commit/PR convention. This Skill encodes that entire procedure so nothing is missed.
Core Features & Use Cases
- Synchronized version bumps: Updates
__version__.py and setup.py together, with rules for when to bump patch versus minor (minor tracks the required dbt-postgres minor).
- CHANGELOG dating: Inserts a dated
## X.Y.Z - YYYY-MM-DD heading under ## Unreleased without rewriting existing bullets, and cross-checks git log so no shipped commit is silently missing from the changelog.
- Standardized release PR: Creates the
dbt-release-X.Y.Z branch, a dbt-materialize: release vX.Y.Z commit, and a PR with a Ship: <url> body targeting MaterializeInc/materialize:main.
- Use Case: A maintainer merges a feature PR into the dbt adapter and asks for the next release; the Skill verifies the unreleased changelog entries, bumps 1.9.9 to 1.9.10, and opens the release PR in one pass.
Quick Start
Ask the assistant to cut a new dbt-materialize release for the feature PR you just merged, and it will bump the version, date the changelog, and open the release PR.