OpenClaw LaunchOpenClaw Launch
🏷️

Release Tagging Strategy

Verified

by Community

Establishes a strategy for tagging releases in Git using semantic versioning. Covers tag naming conventions, annotated vs lightweight tags, pre-release versions, and integration with CI/CD for automated releases.

releasetaggingsemantic-versioning

Release Tagging Strategy

Tag your releases consistently using semantic versioning to communicate the nature of changes. Set up automated tagging that integrates with your CI/CD pipeline for reliable releases.

Usage

Ask about tagging releases, choosing version numbers, or automating the release tagging process.

Examples

  • "How should I tag releases in my Git repository?"
  • "When should I bump the major vs minor vs patch version?"
  • "How do I automate release tagging with semantic-release?"

Guidelines

  • Use annotated tags with release notes for all production releases
  • Follow semantic versioning: major for breaking, minor for features, patch for fixes
  • Use pre-release tags (e.g., v2.0.0-beta.1) for testing before stable release
  • Automate tagging in CI/CD to ensure consistency
  • Never move or delete tags that have been pushed to the remote

More Git & Version Control Skills

✍️
Commit Message Convention

Write clear, consistent commit messages that tell a story.

🪝
Git Hooks Guide

Automate quality checks with client-side and server-side Git hooks.

📏
Git Rebase Workflow

Use Git rebase to maintain a clean, linear commit history.

🔎
Git Bisect Guide

Find the commit that introduced a bug using binary search.