release-please-standards
release-please standards and configuration reference. Use when configuring release workflows, checking automation compliance, or working with version bumps.
How do I install this agent skill?
npx skills add https://github.com/laurigates/claude-plugins --skill release-please-standardsIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides standard configuration templates and guidelines for implementing release-please for automated semantic versioning and changelog generation. It follows industry best practices by utilizing GitHub Secrets for authentication and referencing official actions from trusted organizations.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
1 file scanned · No issues
What does this agent skill do?
Release-Please Standards
When to Use This Skill
| Use this skill when... | Use the alternative instead when... |
|---|---|
| You need the canonical release-please workflow, manifest, and config-file shape | You want to audit or set up release-please end-to-end as an interactive workflow — use configure-release-please |
| You are checking an existing release-please setup against documented conventions | You want runtime detection of repo type and existing config before changes — use configure-release-please |
| Another skill needs to cite the standard release-please configuration | You are configuring monorepo component tags, per-package extra-files, or shared→component tag migration — use git-plugin:release-please-configuration |
Version: 2025.1
Standard release-please configuration for automated semantic versioning and changelog generation.
Standard Configuration
GitHub Actions Workflow
File: .github/workflows/release-please.yml
The release PR needs a token that can trigger other workflows. Two patterns;
the GitHub App token is preferred (the laurigates org standard), with the
MY_RELEASE_PLEASE_TOKEN PAT kept as a legacy fallback.
GitHub App token (preferred) — create-github-app-token mints a token from
RELEASE_PLEASE_APP_ID (variable) and RELEASE_PLEASE_PRIVATE_KEY (secret),
which gitops provisions on repos flagged release_please = true:
name: Release Please
on:
push:
branches:
- main
permissions:
contents: write
pull-requests: write
jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: actions/create-github-app-token@v3
id: app-token
with:
app-id: ${{ vars.RELEASE_PLEASE_APP_ID }}
private-key: ${{ secrets.RELEASE_PLEASE_PRIVATE_KEY }}
- uses: googleapis/release-please-action@v4
with:
token: ${{ steps.app-token.outputs.token }}
PAT (legacy) — a MY_RELEASE_PLEASE_TOKEN secret in repository settings:
- uses: googleapis/release-please-action@v5
with:
token: ${{ secrets.MY_RELEASE_PLEASE_TOKEN }}
Configuration Files
File: release-please-config.json
{
"packages": {
".": {
"release-type": "node",
"changelog-sections": [
{"type": "feat", "section": "Features"},
{"type": "fix", "section": "Bug Fixes"},
{"type": "perf", "section": "Performance"},
{"type": "deps", "section": "Dependencies"},
{"type": "docs", "section": "Documentation", "hidden": true},
{"type": "chore", "section": "Miscellaneous", "hidden": true}
]
}
},
"plugins": ["node-workspace"]
}
File: .release-please-manifest.json
{
".": "0.0.0"
}
Note: Version 0.0.0 is a placeholder - release-please updates this automatically.
Project Type Variations
Node.js Frontend/Backend
- release-type:
node - plugins:
node-workspace - Updates:
package.jsonversion field
Python Service
- release-type:
python - Updates:
pyproject.tomlversion field,__version__in code
Infrastructure (Helm)
- release-type:
helm - Updates:
Chart.yamlversion field
Multi-package Repository
Monorepos need component on every package and include-component-in-tag: true
at the root, plus per-package extra-files and (optionally) the
linked-versions plugin:
{
"packages": {
"packages/frontend": {"release-type": "node", "component": "frontend"},
"packages/backend": {"release-type": "node", "component": "backend"}
},
"plugins": ["node-workspace"]
}
For the full monorepo strategy — component tagging, duplicate-tag / multiple-paths
fixes, per-package extra-files path rules, linked versions, adding a package,
and shared→component tag migration — see git-plugin:release-please-configuration.
Required Components
Minimum Requirements
-
Workflow file:
.github/workflows/release-please.yml- Uses
googleapis/release-please-action@v5 - Token: GitHub App token (preferred) or
MY_RELEASE_PLEASE_TOKENsecret - Triggers on push to
main
- Uses
-
Config file:
release-please-config.json- Valid release-type for project
- changelog-sections defined
-
Manifest file:
.release-please-manifest.json- Lists all packages with current versions
Token Configuration
The workflow uses a dedicated release token (not GITHUB_TOKEN) because:
- Allows release PRs to trigger other workflows
- Enables CI checks on release PRs
- Maintains proper audit trail
Two token patterns are accepted:
| Pattern | How | When |
|---|---|---|
| GitHub App token (preferred) | actions/create-github-app-token → app-id: ${{ vars.RELEASE_PLEASE_APP_ID }}, private-key: ${{ secrets.RELEASE_PLEASE_PRIVATE_KEY }}, passed as token: ${{ steps.app-token.outputs.token }} | laurigates org standard — credentials are gitops-provisioned on release_please = true repos |
| PAT (legacy) | token: ${{ secrets.MY_RELEASE_PLEASE_TOKEN }} | Where the GitHub App isn't set up |
A workflow already using the App-token pattern is compliant — do not flag it to
switch to MY_RELEASE_PLEASE_TOKEN.
Compliance Checking
Status Levels
| Status | Condition |
|---|---|
| PASS | All three files present with valid configuration |
| WARN | Files present but using deprecated action version (older than v5) |
| FAIL | Missing required files or invalid configuration |
Validation Rules
-
Workflow validation:
- Action version:
v5(warn if older) - Token: Must use secret, not hardcoded
- Trigger: Must include
pushtomain
- Action version:
-
Config validation:
- release-type: Must be valid (node, python, helm, simple)
- changelog-sections: Must include feat and fix
-
Manifest validation:
- Must be valid JSON
- Packages must match config
Protected Files
IMPORTANT: Release-please manages these files automatically:
CHANGELOG.md- Never edit manually- Version fields in
package.json,pyproject.toml,Chart.yaml .release-please-manifest.json- Only edit for initial setup
See release-please-protection skill for enforcement.
Conventional Commits
Release-please requires conventional commit messages:
| Prefix | Release Type | Example |
|---|---|---|
feat: | Minor | feat: add user authentication |
fix: | Patch | fix: correct login timeout |
feat!: | Major | feat!: redesign API |
BREAKING CHANGE: | Major | In commit body |
Installation
- Create workflow file
- Create config file
- Create manifest file
- Provide the release token — preferred: set the
RELEASE_PLEASE_APP_IDvariable +RELEASE_PLEASE_PRIVATE_KEYsecret (gitops provisions these onrelease_please = truerepos); legacy: addMY_RELEASE_PLEASE_TOKENto repository secrets - Ensure pre-commit has conventional-pre-commit hook
Troubleshooting
Release PR Not Created
- Check conventional commit format
- Verify workflow has correct permissions
- Ensure token has write access
Version Not Updated
- Check manifest file is valid JSON
- Verify release-type matches project
- Review release-please logs in Actions
CI Not Running on Release PR
- Token must be a dedicated release token (GitHub App token or PAT), not
GITHUB_TOKEN - Verify workflow trigger includes pull_request
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/laurigates/claude-plugins/release-please-standards">View release-please-standards on skillZs</a>