[alexmorbo]

Part of muster-io/muster#62

Story: none (release configuration, maintainer decisions D399 and D394).

release-please now bumps the patch for a feat and the minor for a breaking change while the version is 0.x (bump-patch-for-minor-pre-major), so the libraries stay 0.x until Muster 1.0; the first release stays 0.1.0, because with no previous release release-please takes initial-version without applying any bump rule. Renovate now types a runtime dependency update build(deps): … instead of fix(deps): … only when it rewrites a bound in pyproject.toml, and changelog-sections lists build under "Dependencies" instead of "Bug Fixes"; lock-file-only updates, which are most of them, and the other updates stay chore(deps), hidden and without a release of their own, as before. CONTRIBUTING.md now says that build is for dependency changes and that build-system or tooling work uses chore or ci.

Acceptance evidence

Check	Evidence
JSON valid	jq . release-please-config.json
Renovate config valid	renovate-config-validator --strict .github/renovate.json5: Config validated successfully

verify output

Not applicable: configuration only.

Story file changed in muster-io/muster: why

None.

Dependencies

None added.

Maintainer steps

None.