release-version

Create Orient releases with versioning, changelog updates, and Docker image tags.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/orient-bot/orient --skill release-version-orient-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-version
Source: https://github.com/orient-bot/orient/tree/main/.claude/skills/release-version
Command: npx skills add https://github.com/orient-bot/orient --skill release-version-orient-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear, step-by-step guide and automated process for creating new releases of the Orient project, ensuring proper versioning, changelog updates, and Docker image tagging.

Core Features & Use Cases

  • Version Control: Guides users through Semantic Versioning and pre-release tagging.
  • Changelog Management: Details how to update CHANGELOG.md with new additions, changes, and fixes.
  • Automated Workflows: Explains the automatic GitHub release creation and Docker image tagging triggered by release tags.
  • Use Case: A developer needs to prepare and publish a new stable version of Orient. They follow this Skill's instructions to update the changelog, create a Git tag, and push it, which then automatically generates a GitHub release and tags Docker images.

Quick Start

Follow the steps in this guide to update the changelog and create a new release tag for version X.Y.Z.

Frequently Asked Questions about release-version

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

FAQPage Schema
How do I create a new release with proper Git tags and Docker image tagging?

Automated GitHub Actions handle Docker image tagging and GitHub Release creation immediately after you push a Git tag. You must manually update CHANGELOG.md and create the version tag locally before pushing to trigger these workflows.

How does changelog management work for a new version?

Changelog management involves manually updating CHANGELOG.md with new additions, changes, and fixes for version X.Y.Z. The Skill provides a step-by-step guide to ensure these entries are properly structured before tagging.

What is the pre-release checklist for preparing a stable version?

The pre-release checklist covers verifying Semantic Versioning rules, updating CHANGELOG.md, and confirming all code changes are committed. Following these steps ensures a clean Git tag and successful automated deployment.

Can I use GitHub Actions to automate Docker image tagging for releases?

Yes, GitHub Actions automatically tag Docker images when you push a Git tag. The Skill explains how these automated workflows handle Docker image tagging and GitHub Release creation upon detecting the release tag.

Why is my release version not triggering the automated GitHub Release creation?

Release creation fails if the Git tag does not follow Semantic Versioning or if the GitHub Actions workflow is misconfigured. The Skill includes troubleshooting steps for common release issues to help diagnose these automation failures.

What are the limitations of using pre-release tagging for version control?

Pre-release tagging limitations involve potential conflicts with automated Docker image tagging if the format deviates from expected Semantic Versioning. The Skill provides troubleshooting steps to resolve these common release issues.