provider-release

What problem does it solve?

It solves the problem of releasing and versioning MQL providers manually, which is error-prone and makes it hard to ensure PRs include the right version bumps and changelogs.

Core Features & Use Cases

• Detect provider changes: Identify which providers have changed since their last version bump, across all providers or a selected subset.
• Bump versions and generate changelogs: Update provider versions (patch/minor/major) and generate release content derived from commit history.
• Create release PRs: Commit the version changes, push the branch, and prepare a pull request for the provider release workflow.

Use cases include preparing a release PR after feature merges, bumping versions consistently across cloud providers (e.g., aws/gcp/azure), and checking which providers actually need a release.

Quick Start

Run the provider change check, then bump only the providers you confirm into a version-release PR.