diff --git a/.claude/skills/release/SKILL.md b/.claude/skills/release/SKILL.md index fe3c901..376c4f9 100644 --- a/.claude/skills/release/SKILL.md +++ b/.claude/skills/release/SKILL.md @@ -10,6 +10,14 @@ Bumping `version` in `package.json` on `main` is the release button. The that version's CHANGELOG section as notes, and dispatches `release.yml`, which deploys to GitHub Pages (https://seriesoftub.es). +## Not everything needs a release + +Release only when there is something worth shipping to players: a feature, a fix they +will notice, or a decent batch of smaller changes. Docs, skills, CI, issue templates, +tests and refactors never need a release on their own; just push them. Small +player-facing tweaks can sit under `## [Unreleased]` until a real release comes along. +Don't plan a release just because the hour is up, and when unsure, ask the user. + ## At most one release per hour Players get an update banner and a "What's new" window for every release, so ship at diff --git a/CLAUDE.md b/CLAUDE.md index f68ee15..c9dbd5c 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -28,7 +28,7 @@ To play during development, open `site/index.html` directly or run `npm run serv or any other attribution trailers. - **Releases** happen by bumping `version` in `package.json` on `main` (see the `release` skill). Small fixes or tweaks get a patch release (`x.y.Z`); new features a - minor release. **At most one release per hour**: until the hour is up, push work with + minor release. **Not everything needs a release**: docs, skills, CI, tests and refactors are just pushed, and small player-facing tweaks wait under `## [Unreleased]` for a real release. **At most one release per hour**: until the hour is up, push work with its CHANGELOG bullets under `## [Unreleased]` and batch it into the next release. Only a broken live game justifies an immediate hotfix. - **Release notes in the app are short**: only the first sentence of each CHANGELOG bullet