skills.rest
Nick777-Pixel
Nick777-PixelCOMMUNITY
Explore all skills by this author →
GitHub

version-release

Automate version release workflows across canary and main branches.

Updated Apr 3, 2026
Search Tags:#automation#git#versioning#release#ci-cd#branch-management
One-click install
npx skills add https://github.com/Nick777-Pixel/mychat7 --skill version-release-nick777-pixel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version-release
Source: https://github.com/Nick777-Pixel/mychat7/tree/main/.agents/skills/version-release
Command: npx skills add https://github.com/Nick777-Pixel/mychat7 --skill version-release-nick777-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the version release workflow across canary and main branches, handling branch creation, version calculation, PR orchestration, and post-release tasks to reduce manual toil and ensure consistent releases.

Core Features & Use Cases

  • Minor Release Workflow: Create a release branch from canary, determine the next minor version, open a PR to main with a standardized title, and let CI auto tag and publish the release.
  • Patch Release Workflow: Weekly releases or hotfixes from canary or main, automatically bumping the patch version, enabling multiple scenarios including weekly schedules, model launches, and migrations.
  • Auto-Release Triggers & Post-Release Actions: Rules for triggering releases based on branch names and PR titles; CI generates changelogs, bumps versions, creates GitHub Releases, and syncs main back to canary.

Quick Start

Create a release/v{version} branch from canary and submit a PR to main with the required title to initiate a minor release workflow.

Frequently Asked Questions about version-release

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

FAQPage Schema
How do I automate a minor version release workflow from a canary branch?▼

Patch releases like weekly updates or hotfixes are automated from canary or main, automatically bumping the patch version and triggering CI to generate changelogs and publish the release.

What happens to canary and main branches after a release is published?▼

After post-release synchronization, the workflow automatically syncs the main branch back to canary, ensuring both branches remain consistent and ready for the next development cycle.

Can I use automated version bumping for both scheduled weekly releases and hotfixes?▼

Yes, automated version bumping supports multiple scenarios including scheduled weekly releases, hotfixes, model launches, and migrations by applying patch version increments from canary or main branches.

Do I need to manually generate changelogs when automating continuous deployment releases?▼

No, manual changelog generation is not needed. The release workflow's CI pipeline automatically generates changelogs, bumps versions, and creates GitHub Releases based on branch names and PR titles.

What are the limitations of using standardized PR titles for release triggers?▼

This release workflow requires strict source-branch handling and specific PR title formatting to trigger correctly. It currently supports Minor and Patch releases, meaning Major version bumps are outside its supported scope.

Related Skills

Explore More Software Engineering Skills→
StaysrStaysr

version-release

Automate version tagging, changelog generation, and PR workflows for minor and patch releases.

Community
Advanced
richardrimanrichardriman
2

crafter-release

Automate GitHub releases with notes and binary uploads via gh CLI.

Community
Advanced
5hdaniel5hdaniel

release

Automate release management with version bumping, branch merging, tagging, and pushing.

Community
Intermediate
im9im9
1

release

Automate versioning, changelog generation, and release deployment via PR-based workflows.

Community
Advanced