From 463c19fe7f7e85eebc2e0c70619551e1c61c9a9b Mon Sep 17 00:00:00 2001 From: david morales <118213696+davidmoralesz@users.noreply.github.com> Date: Fri, 9 Oct 2026 14:35:55 -0600 Subject: [PATCH] fix(docs): say a change to a managed file must be a fix or feat to ship The monthly Dependabot block merged as a chore, which release-please does not release, so sync kept pulling v0.3.1 with weekly. Document the trap, and let this commit be the release that carries the Dependabot change. --- CONTRIBUTING.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 36f67df..8da7613 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -66,6 +66,10 @@ markers, are kept in step with `studiobimo/project-template`. Change them there, `make -C .devtools sync` brings the change in. `make -C .devtools drift` shows what differs, and a weekly workflow opens an issue when something does. A deliberate difference goes in `.template-ignore`, with a comment saying why. + +Projects only receive a change at a release, and release-please releases only `fix`, `feat` and +breaking commits. A change to a managed file titled `chore`, `docs` or `ci` merges but never reaches +`sync`, so title it `fix` or `feat`. ## Releases