skills.rest
tomazb
tomazbCOMMUNITY
Explore all skills by this author →
GitHub

release

Automate version bumps across Python, Bash, Helm, README, changelog, and container files.

3|1|Updated Nov 18, 2025
Search Tags:#automation#changelog#python#bash#release#helm#version-bump
One-click install
npx skills add https://github.com/tomazb/rh-acm-switchover --skill release-tomazb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/tomazb/rh-acm-switchover/tree/main/.claude/skills/release
Command: npx skills add https://github.com/tomazb/rh-acm-switchover --skill release-tomazb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual version bumps across Python modules, shell helpers, README, changelog, and deployment metadata leave release statements inconsistent and slow down safe cutovers.

Core Features & Use Cases

  • Consistent metadata updates: refreshes lib/__init__.py, scripts/constants.sh, container-label versions, and Helm chart fields to match the supplied semver.
  • Changelog release promotion: moves existing unreleased entries into a new version section dated with today's release, keeping the history accurate.
  • Use Case: Before shipping a new ACM switchover release, run the automation to guarantee every documented version and deployment artifact reflects the same number and date.

Quick Start

Invoke the release skill with the target version, for example /release 1.6.3, to sync every version marker across the repo.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumps across Python, Bash, and Helm files?▼

Automating version bumps across Python, Bash, and Helm files requires updating six key project files simultaneously. This skill syncs version markers in modules, shell scripts, charts, and changelogs using a single semantic version argument.

What is the best way to align every file to a new release version?▼

Aligning every file to a new release version is done by passing a semantic version to an automation script. It updates Python modules, shell constants, container labels, Helm fields, README, and changelog sections to match the supplied number.

How does changelog release promotion work when preparing a new version?▼

Changelog release promotion works by moving existing unreleased entries into a newly created version section. The automation inserts today's date for the release while preserving the unreleased entries, keeping the history accurate and synced with the version bump.

Can I use this release automation for Red Hat ACM switchover preparation?▼

Yes, this release automation is specifically designed for the Red Hat ACM switchover repository. It guarantees that every documented version and deployment artifact reflects the same number and date before shipping a new release.

Do I need a specific semantic version format to sync version markers?▼

You need to provide a valid semantic version argument to sync version markers across the repository. The automation expects this argument to update Python, Bash, Helm, README, changelog, and container files consistently.

Related Skills

Explore More Software Engineering Skills→
yangwhaleyangwhale
9

deepep-installer

Install, configure, and troubleshoot DeepEP on NVIDIA GPU systems.

Community
Advanced
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
lakshitadidwania2106lakshitadidwania2106
1

changelog-writer

Generate Bifrost release changelogs from git history and module dependencies.

Community
Advanced
BagelHoleBagelHole
46

semantic-versioning

Automate version bumps and changelog generation from Conventional Commits.

Community
Advanced