FVH (Forum Virium Helsinki) release-please standards and configuration. Use when configuring release-please workflows, checking release automation compliance, or when the user mentions FVH release-please, automated releases, or version management.
/plugin marketplace add laurigates/claude-plugins/plugin install configure-plugin@lgates-claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
FVH standard release-please configuration for automated semantic versioning and changelog generation.
File: .github/workflows/release-please.yml
name: Release Please
on:
push:
branches:
- main
permissions:
contents: write
pull-requests: write
jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: googleapis/release-please-action@v4
with:
token: ${{ secrets.MY_RELEASE_PLEASE_TOKEN }}
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.
nodenode-workspacepackage.json version fieldpythonpyproject.toml version field, __version__ in codehelmChart.yaml version field{
"packages": {
"packages/frontend": {
"release-type": "node",
"component": "frontend"
},
"packages/backend": {
"release-type": "node",
"component": "backend"
}
},
"plugins": [
"node-workspace",
{
"type": "linked-versions",
"groupName": "workspace",
"components": ["frontend", "backend"]
}
]
}
Workflow file: .github/workflows/release-please.yml
googleapis/release-please-action@v4MY_RELEASE_PLEASE_TOKEN secretmainConfig file: release-please-config.json
Manifest file: .release-please-manifest.json
The workflow uses MY_RELEASE_PLEASE_TOKEN secret (not GITHUB_TOKEN) because:
| Status | Condition |
|---|---|
| PASS | All three files present with valid configuration |
| WARN | Files present but using deprecated action version |
| FAIL | Missing required files or invalid configuration |
Workflow validation:
v4 (warn if older)push to mainConfig validation:
Manifest validation:
IMPORTANT: Release-please manages these files automatically:
CHANGELOG.md - Never edit manuallypackage.json, pyproject.toml, Chart.yaml.release-please-manifest.json - Only edit for initial setupSee release-please-protection skill for enforcement.
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 |
MY_RELEASE_PLEASE_TOKEN to repository secretsThis skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.