skills.rest
kingmacth
kingmacthCOMMUNITY
Explore all skills by this author →
GitHub

version-release

Orchestrate canary-to-main version releases with automated tagging and changelog generation.

Updated Dec 12, 2024
Search Tags:#automation#changelog#versioning#branching#release#ci-cd#git-workflow
One-click install
npx skills add https://github.com/kingmacth/lobe-chat --skill version-release-kingmacth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version-release
Source: https://github.com/kingmacth/lobe-chat/tree/main/.agents/skills/version-release
Command: npx skills add https://github.com/kingmacth/lobe-chat --skill version-release-kingmacth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Version release workflow automation tackles the friction of coordinating code merges, version bumps, changelog creation, and release tagging across multiple branches, providing a repeatable, auditable process.

Core Features & Use Cases

  • Minor Release Workflow: publish a new minor version from canary to main with automated tagging and changelog generation.
  • Patch Release Workflow: perform weekly or hotfix releases with automatic patch bumps and release notes; supports multiple scenarios (weekly releases, hotfixes, migrations).
  • Auto-Release Triggers & Post-Release Actions: triggers CI-tagged releases based on branch names or PR titles; updates and syncing policies. This workflow is applicable to teams using canary/main branching models and automated release pipelines in CI/CD environments.

Quick Start

Follow the Minor Release steps to create a release branch from canary, increment the version, open a PR to main with the required title, and let the automation publish the release.

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 from a canary branch to main?▼

To automate a minor version release, you create a release branch from canary, increment the version, open a PR to main with the required title, and let the automation publish the release with automated tagging and changelog generation.

What is the best way to handle emergency hotfix versioning in a CI/CD pipeline?▼

For emergency hotfix versioning, the patch release workflow applies automatic patch bumps and generates release notes, supporting hotfix scenarios alongside weekly releases within your branch-based release pipeline.

Does this automation support canary-to-main branching models for release workflows?▼

Yes, this workflow is explicitly applicable to teams using canary-to-main branching models and automated release pipelines in CI/CD environments, orchestrating end-to-end version release workflows.

How do CI-tagged release triggers work with branch names and PR titles?▼

Auto-release triggers initiate CI-tagged releases based on specific branch names or PR titles, automating the version bump and subsequent post-release synchronization tasks across branches.

What post-release synchronization tasks are needed after an automated version bump?▼

Post-release synchronization tasks involve applying updates and syncing policies to ensure branches remain consistent after the automated version bump, tagging, and changelog generation complete across the release pipeline.

Related Skills

Explore More Software Engineering Skills→
chrishuffman5chrishuffman5

upload-skill

Automate publishing skill folders to the main branch and trigger CI/CD deployment.

Community
Advanced
haJ1thaJ1t

release-manager

Automate release management by parsing conventional commits and generating changelogs.

Community
Advanced
tethertotetherto
395

sdk-backmerge

Create pull requests to backmerge release version bumps and changelogs into main.

Official
Advanced
zmh13928433602-syszmh13928433602-sys

version-release

Automate release planning, version bumps, and GitHub Release notes.

Community
Advanced