Skip to content
Skills Library
DevOps & cloud · Automation

release-please-development

/release-please-development

This skill should be used when the user asks to "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", or mentions release-please, semantic versioning, or monorepo versioning.

Licence
MIT
Last repository change
10.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

This skill should be used when the user asks to "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", or mentions release-please, semantic versioning, or monorepo versioning.

Triggers from the description

set up release pleaseconfigure automated releasesmanage version numbersadd changelog automation
Original author description

This skill should be used when the user asks to "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", or mentions release-please, semantic versioning, or monorepo versioning.

How it works

  1. Quick Reference
  2. Overview
  3. Core Files
  4. When to Use Each Pattern
  5. Basic Setup
  6. Release Types
  7. Updating Extra Files
  8. Claude Code Plugin Marketplaces
  9. Conventional Commits
  10. How It Works
Original SKILL.md headings · 173 lines, 481 words
SKILL.md preview
---
name: release-please-development
description: This skill should be used when the user asks to "set up release please", "configure automated releases", "manage version numbers", "add changelog automation", or mentions release-please, semantic versioning, or monorepo versioning.
allowed-tools: Read, Grep
---

# Release Please Development

Configure automated versioning, changelog generation, and releases using Google's release-please.

## Quick Reference

- [Single Package Pattern](./references/examples/single-package.md) - Simple repos with one version
- [Multi-Package Pattern](./references/examples/multi-package.md) - Monorepos with independent versions
- [Configuration Options](./references/configuration.md) - All available settings

## Overview

Release-please automates:
- Version bumping based on conventional commits
- CHANGELOG.md generation
- GitHub release creation
- Version updates in files (package.json, Chart.yaml, etc.)

## Core Files

```
.github/
├── release-please-config.json    # Package configuration
├── release-please-manifest.json  # Current version tracking
└── workflows/
    └── release.yaml              # GitHub Actions workflow
```

## When to Use Each Pattern

| Pattern | Use Case |
|---------|----------|
| Single Package | Libraries, CLIs, simple apps with one version |
| Multi-Package | Monorepos, services with independent release cycles |

## Basic Setup

### 1. Create Config File

`.github/release-please-config.json`:

```json
{
  "release-type": "simple",
  "packages": {
    ".": {
      "changelog-path": "CHANGELOG.md"
    }
  }
}
```

### 2. Create Manifest

`.github/release-please-manifest.json`:

```json
{
  ".": "0.0.1"
}
```

### 3. Add GitHub Workflow

`.github/workflows/release.yaml`:

```yaml
name: Release

on:
  push:
    branches: [main]

permissions:
  contents: write
  pull-requests: write

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: googleapis/release-please-action@v4
        with:
          config-file: .github/release-please-config.json
          manifest-file: .github/release-please-manifest.json
```

## Release Types

| Type | Use Case | Versions |
|------|----------|----------|
| `simple` | Generic projects | CHANGELOG only |
| `node` | npm packages | package.json |
| `python` | Python packages | setup.py, pyproject.toml |
| `go` | Go modules | go.mod |
| `helm` | Helm charts | Chart.yaml |

## Updating Extra Files

Use `extra-files` to update versions in arbitrary files:

```json
{
  "packages": {
    ".": {
      "extra-files": [
        {
          "type": "json",
          "path": "manifest.json",
          "jsonpath": "$.version"
        }
      ]
    }
  }
}
```

## Claude Code Plugin Marketplaces

For marketplaces with multiple plugins sharing a single version:

```json
{
  "release-type": "simple",
  "packages": {
    ".": {
      "changelog-path": "CHANGELOG.md",
      "extra-files": [
        {
          "type": "json",
          "path": ".claude-plugin/marketplace.json",
          "jsonpath": "$.plugins[0].version"
        },
        {
          "type": "json",
          "path": ".claude-plugin/marketplace.json",
          "jsonpath": "$.plugins[1].version"
        }
      ]
    }
  }
}
```

Add a jsonpath entry for each plugin in the marketplace. When adding new plugins, update both:
1. `.claude-plugin/marketplace.json` - add the plugin entry
2. `.github/release-please-config.json` - add jsonpath for the new plugin's version

## Conventional Commits

Release-please uses commit prefixes to determine version bumps:

| Prefix | Version Bump | Example |
|--------|--------------|---------|
| `feat:` | Minor (0.x.0) | New feature |
| `fix:` | Patch (0.0.x) | Bug fix |
| `feat!:` or `BREAKING CHANGE` | Major (x.0.0) | Breaking change |
| `docs:`, `chore:`, etc. | None | No release |

## How It Works

1. Push commits to main with conventional commit messages
2. Release-please creates/updates a release PR
3. Merge the release PR to create a GitHub release
4. Tags and changelog are automatically generated

## See Also

- [Single Package Example](./references/examples/single-package.md) - Detailed single-package setup
- [Multi-Package Example](./references/examples/multi-package.md) - Monorepo configuration
- [Configuration Reference](./references/configuration.md) - All options explained
Files in this package (4)
  • SKILL.md 4 KB
  • references/configuration.md 6 KB
  • references/examples/multi-package.md 6 KB
  • references/examples/single-package.md 3 KB

Versions

The database has no other skills named release-please-development.

Database snapshot: 13.11.2026 · package version 6443f47e8cb6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100semantic-versioning
    Automate versioning and changelog generation using semantic versioning principles. Configure release automation, version bumping, and changelog tools. Use when implementing version management or automating release processes.
  • 100release-please
    Use when adopting or operating Release Please for automated versioning, changelog generation, and GitHub releases in single-package or manifest-mode repositories
  • 100release-versioning-and-changelog-automation
    Establishes a version numbering scheme (SemVer or CalVer) and automates changelog generation and release tagging from commit history, typically via Conventional Commits and tools like semantic-release or release-please. Use when the user asks to "set up semantic versioning,"…
  • 100release
    This skill should be used when the user asks about "release process", "versioning", "semantic versioning", "semver", "release automation", "publishing", "package publishing", "release checklist", "version bump", "release notes", or needs guidance on release workflows and version management.
  • 87release-please
    Set up and configure Google's release-please for automated versioning, changelog generation, and publishing via GitHub Actions. Covers pipeline creation, Conventional Commits formatting, pre-release workflows, monorepo configuration, and troubleshooting release pipelines. Use…
  • 100release
    Use when you prepare a release or choose a version number. Links the versioning and safety rules. Does not publish.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.