skills.rest
mondoohq
mondoohqOFFICIAL
Explore all skills by this author →
Website𝕏@mondoohqGitHub

provider-release

Automate MQL provider release PRs by checking changes, bumping versions, and generating changelogs.

407|38|Updated Aug 16, 2022
Search Tags:#git commit#release workflow#version bump#changelog generation#pull request automation#provider release#mql providers
One-click install
npx skills add https://github.com/mondoohq/mql --skill provider-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: provider-release
Source: https://github.com/mondoohq/mql/tree/main/.claude/skills/provider-release
Command: npx skills add https://github.com/mondoohq/mql --skill provider-release

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about provider-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate version bumps and changelog generation for MQL provider releases?▼

Check provider change status by running the release workflow against scoped provider paths to identify which MQL providers have changed since their last version bump across all providers or a selected subset.

Can I batch version bumps across multiple cloud providers like AWS, GCP, and Azure?▼

Commit version changes, push the branch, and prepare a pull request for the provider release workflow. The workflow handles commit automation and can generate an optional PR output file to use with external pull request automation tools.

How do I check which MQL providers have changed and actually need a release?▼

Detect provider changes by running the provider change check to see which providers have changed since their last version bump. This targets all providers or a selected subset, helping you confirm exactly what needs a release before bumping versions.

Does the MQL provider release workflow support patch, minor, and major version increments?▼

The provider release workflow supports deterministic version increment options including patch, minor, and major bumps. It invokes the Go-based providers-sdk version utility with scoped provider paths to apply the selected increment type consistently.

What's the best way to create a release PR after merging features into MQL providers?▼

Run the provider change check, bump only the confirmed providers into a version-release PR. The workflow commits the version changes, pushes the branch, and prepares the pull request with changelog content derived from commit history.

Related Skills

Explore More Software Engineering Skills→
ToXMonToXMon

akash

Update Akash Network documentation with corrected CLI commands and SDK import paths.

Community
Advanced
sefllessseflless

update-release-notes

Aggregate merged PRs into next.mdx and archive release notes on new versions.

Community
Intermediate
zli5460zli5460
2

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merging.

Community
Intermediate
gittowergittower
413

release

Update changelog and version files from git history using semantic versioning.

Official
Advanced