release-please

Automate GitHub releases and version bumps from conventional commits.

Updated Feb 24, 2026

Search Tags:#github #github actions #release automation #version bumping #changelog management

Ready to run

npx skills add https://github.com/Exar-lab/Bank-project --skill release-please-exar-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-please
Source: https://github.com/Exar-lab/Bank-project/tree/main/.agents/skills/release-please
Command: npx skills add https://github.com/Exar-lab/Bank-project --skill release-please-exar-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, release-please-config.json, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating GitHub releases, bumping versions, and updating CHANGELOG.md for your projects, saving time and reducing errors in release management.

Core Features & Use Cases

Automated Release Creation: Automatically create GitHub releases based on commit history.
Version Bumping: Bump versions based on commit types (major, minor, patch).
CHANGELOG.md Management: Update CHANGELOG.md with new release information.
Use Case: Imagine you have a project with a complex versioning system. Use this Skill to automate the release process, ensuring consistent and accurate versioning across all releases.

Quick Start

Run the release-please GitHub Action on your master branch to create a new release.

Frequently Asked Questions about release-please

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

FAQPage Schema

How do I automate GitHub releases and version bumping based on commits?▼

Automate GitHub releases and version bumping by running a GitHub Action on your master branch that parses conventional commit messages to generate new releases and update CHANGELOG.md automatically.

Does release-please work with conventional commit standards for changelog management?▼

Yes, release-please works with conventional commit standards to determine version bump types and organize changelog sections, using a configuration file to define the specific release behavior and changelog structure.

How do I configure changelog sections in release-please?▼

Configure changelog sections in release-please by defining the desired release behavior and section groupings within a release-please-config.json file, which guides how the Action parses commits and updates CHANGELOG.md.

What do I need to set up before running release-please on my repository?▼

Before running release-please, you need GitHub API access, a properly configured release-please-config.json file, and a GitHub Action set up on your master branch to trigger the automated release process.

Why are my version bumps not triggering correctly in GitHub Actions?▼

Version bumps may not trigger correctly if commit messages do not adhere to conventional commit standards, or if the release-please configuration file lacks the proper definitions for release behavior and version bumping rules.

Can I use release-please to manage complex versioning systems across multiple releases?▼

Yes, you can use release-please to manage complex versioning systems by automating the release process through GitHub Actions, ensuring consistent and accurate version bumping and changelog updates across all project releases.