release-new-version

Release Ruby SDK versions to Ruby Gems with version bumps and changelog updates.

13|8|Updated Apr 2, 2026

Search Tags:#changelog #sdk #release #ruby #tagging #version #rubygems

Ready to run

npx skills add https://github.com/datagouv/apistration --skill release-new-version-datagouv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-new-version
Source: https://github.com/datagouv/apistration/tree/main/clients/.claude/skills/release-new-version
Command: npx skills add https://github.com/datagouv/apistration --skill release-new-version-datagouv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing a new Ruby SDK version to rubygems involves coordinating version bumps, changelogs, release PRs, tag conventions, and an OIDC publishing workflow. This Skill standardizes and streamlines that process so teams can publish consistent, compliant releases.

Core Features & Use Cases

Version bump for api_entreprise and api_particulier gems, ensuring independent versioning.
Automated CHANGELOG updates and release PR generation following Keep a Changelog standards.
Tag management and CI/OIDC publishing workflow to rubygems.

Quick Start

Bump the gem version, update the changelog, open a release PR, tag the release, and trigger the rubygems publish process.

Frequently Asked Questions about release-new-version

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

FAQPage Schema

How do I release a new Ruby gem version to rubygems using an OIDC publishing workflow?▼

To release a new Ruby gem version to rubygems, you bump the gem version, update the CHANGELOG, open a release PR, tag the release, and trigger the CI OIDC publishing workflow on rubygems.

What is the process for bumping api_entreprise and api_particulier gem versions independently?▼

Bumping api_entreprise and api_particulier gem versions requires applying independent version increments to each gem, ensuring their distinct release cycles are maintained within the same repository structure.

How do I generate a release PR and update the CHANGELOG for a Ruby SDK?▼

Generating a release PR and updating the CHANGELOG for a Ruby SDK follows Keep a Changelog standards to document changes, then opening a pull request to review version bumps before tagging.

Do I need trusted publisher setup on Rubygems before publishing an SDK with OIDC?▼

Yes, a trusted publisher setup on Rubygems is a required precondition, ensuring the tag-based CI workflow can securely authenticate and publish the SDK using OIDC without API keys.

What tag conventions should I apply when releasing a Ruby SDK to rubygems?▼

Releasing a Ruby SDK to rubygems requires applying consistent tag conventions tied to a tag-based workflow, ensuring CI checks recognize the release trigger and initiate the OIDC publishing process.

Can I use this release workflow if my Ruby repository lacks CI checks?▼

No, this release workflow enforces preconditions including a repository structure with CI checks, a tag-based workflow, and trusted publisher setup to ensure compliant rubygems publishing.