Problem
release-please only opens a release PR for feat, fix, perf, revert and breaking changes; ci, chore, docs, refactor, test, build, style are hidden types and produce nothing. #69 shipped the PR lint — a change every adopter sees in CI — as ci:, and release-please answered No user facing commits found … skipping. Nothing in skills/release-management or skills/branch-and-commit says which types release, or what to do when a hidden-type change must ship (a Release-As: X.Y.Z footer, which docs/setup/bootstrap.md mentions only for the first release).
Fix
skills/branch-and-commit rule 3 ("pick the type deliberately — release-please reads it"): name the two groups.
skills/release-management: a pitfall for "release-worthy change under a hidden type", with the Release-As: footer recipe — in the PR body, since squash_merge_commit_message=PR_BODY makes the body the commit message.
Acceptance
make verify green; this PR's body carries Release-As: 0.5.2 and release-please opens chore: release 0.5.2 from it.
Problem
release-please only opens a release PR for
feat,fix,perf,revertand breaking changes;ci,chore,docs,refactor,test,build,styleare hidden types and produce nothing. #69 shipped the PR lint — a change every adopter sees in CI — asci:, and release-please answeredNo user facing commits found … skipping. Nothing inskills/release-managementorskills/branch-and-commitsays which types release, or what to do when a hidden-type change must ship (aRelease-As: X.Y.Zfooter, whichdocs/setup/bootstrap.mdmentions only for the first release).Fix
skills/branch-and-commitrule 3 ("pick the type deliberately — release-please reads it"): name the two groups.skills/release-management: a pitfall for "release-worthy change under a hidden type", with theRelease-As:footer recipe — in the PR body, sincesquash_merge_commit_message=PR_BODYmakes the body the commit message.Acceptance
make verifygreen; this PR's body carriesRelease-As: 0.5.2and release-please openschore: release 0.5.2from it.