skills.rest
mpaulosky
mpauloskyCOMMUNITY
Explore all skills by this author →
GitHub

release-process-base

Automate version bumping, branch merging, tagging, and CI/CD verification for Git-backed releases.

Updated Mar 18, 2022
Search Tags:#ci/cd#versioning#github#release#semver#tagging#merge-strategy
One-click install
npx skills add https://github.com/mpaulosky/dotfiles --skill release-process-base
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process-base
Source: https://github.com/mpaulosky/dotfiles/tree/main/BaseNewProjectFiles/.squad/skills/release-process-base
Command: npx skills add https://github.com/mpaulosky/dotfiles --skill release-process-base

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies repeatable release procedures so teams avoid manual, error-prone steps when versioning, merging, tagging, and validating CI/CD during releases across ecosystems.

Core Features & Use Cases

  • Version Bumping Patterns: Supports static file bumps, tool-computed versions (NBGV, Maven, Cargo), and tag-only strategies with guidance on where to perform commits.
  • Release PR and Merge Strategies: Decision trees for merge commit, squash, and rebase approaches and recommendations for long-lived vs single-branch models.
  • Tagging, GitHub Releases, and CI Verification: Procedures for annotated tagging, gh release creation, and verifying that workflows trigger and publish artifacts.
  • Diagnostics & Anti-Patterns: Common failure modes, fixes for version mismatches, merge conflicts, and publishing credential issues, plus playbook binding via .release-config.json.

Quick Start

Prepare a release by bumping the version in version.json, creating a Release PR from dev to main, merging with the chosen strategy, tagging v1.2.3, and verifying CI/CD jobs and artifact publication.

Frequently Asked Questions about release-process-base

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

FAQPage Schema
How do I automate semantic versioning and tagging for a Git release workflow?▼

Automate semantic versioning and tagging by bumping the version in a static file, merging via a Release PR, creating an annotated v1.2.3 tag, and validating CI/CD triggers.

What's the best way to merge a release branch into main using GitHub?▼

The best way to merge a release branch into main depends on your model: use decision trees for merge commit, squash, or rebase strategies to satisfy PR-based release merges.

Do I need a specific CI/CD pipeline to use tag-only versioning for releases?▼

No specific CI/CD pipeline is required for tag-only versioning; it supports tool-computed versions for generic projects and validates CI trigger workflows during artifact publication.

Why does my GitHub release workflow fail with version mismatches and publishing credential issues?▼

Release workflows fail with version mismatches and publishing credential issues due to common failure modes; fixes involve checking .release-config.json bindings and validating CI verification procedures.

Can I use a single release workflow for both .NET and Node.js projects?▼

Yes, you can use a single framework-agnostic release workflow for .NET, Node.js, Python, Java, and generic projects by binding configurations via a project playbook or .release-config.json.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
oogDZoogDZ

post-release

Validate GitHub Release notes, CHANGELOG updates, and deployment statuses after publication.

Community
Intermediate
albertoiruruetaalbertoirurueta

setup-java-github-workflows

Automate CI/CD workflow setup for Java/Maven projects with GitHub Actions.

Community
Advanced
Vivekmano27Vivekmano27

release-manager

Automate versioning, changelog generation, and release procedures for git-based projects.

Community
Advanced