skills.rest
bga23
bga23COMMUNITY
Explore all skills by this author →
GitHub

nemoclaw-maintainer-cut-release-tag

Bump version strings and tag main with an annotated semver release.

Updated Aug 23, 2026
Search Tags:#automation#release#semver#pr#tagging#version-bump#repo-management
One-click install
npx skills add https://github.com/bga23/NemoClaw --skill nemoclaw-maintainer-cut-release-tag-bga23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nemoclaw-maintainer-cut-release-tag
Source: https://github.com/bga23/NemoClaw/tree/main/.agents/skills/nemoclaw-maintainer-cut-release-tag
Command: npx skills add https://github.com/bga23/NemoClaw --skill nemoclaw-maintainer-cut-release-tag-bga23

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cut Release Tag automates the end-to-end release workflow for NemoClaw by bumping all version strings and applying tags, reducing manual release toil.

Core Features & Use Cases

  • Bumps version strings across root, plugin, blueprint.yaml, installer defaults, docs config, and versioned doc links.
  • Opens a release PR and, after merge, tags main with an annotated release tag and updates the latest tag.
  • Supports preparing a deployment, shipping a build, or tagging a new software release.

Quick Start

Bump versions, open a release PR, and tag after merge.

Frequently Asked Questions about nemoclaw-maintainer-cut-release-tag

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

FAQPage Schema
How do I automate version bumps and release tagging across a repository?▼

Automating version bumps and release tagging uses a script to update version strings across root, plugin, docs, and installer defaults, then opens a release PR and applies an annotated semver tag to main after merge.

What is the best way to manage semver version string updates in multiple config files?▼

Managing semver version string updates across multiple config files is handled by running bump-version.ts, which synchronizes root, plugin, blueprint.yaml, installer defaults, and versioned doc links.

How does a release PR workflow handle tagging main after merge?▼

A release PR workflow handles tagging main after merge by applying an annotated semver release tag to the main branch and updating the latest tag once the version bump PR is merged.

Can I run build and tests as part of an automated release workflow?▼

You can run build and tests as part of an automated release workflow by executing them within the version bump process, ensuring validation before the release PR is opened and the semver tag is applied.

When do I need an annotated semver tag for a software release?▼

You need an annotated semver tag for a software release when preparing a deployment or shipping a build, as it marks the specific commit on main with release version metadata and updates the latest tag.

Related Skills

Explore More Software Engineering Skills→
NVIDIANVIDIA
22.1k

nemoclaw-maintainer-cut-release-tag

Automates semver release tagging and version string updates for NemoClaw.

Official
Advanced
Conceptual-MachinesConceptual-Machines
195

release

Create and push a v-prefixed git tag on the main branch.

Official
Intermediate
dataroadincdataroadinc
1

release-prep

Automate Rust release workflows by bumping versions, validating changes, and opening pull requests.

Official
Advanced
mizchimizchi
320

conventional-changelog

Generate CHANGELOGs from Conventional Commits with semver tagging.

Community
Advanced