chore(release): release breaking changes as minor

[KyleJune]

Why

.releaserc.json mapped breaking changes to a major release, so the next breaking change would have published 1.0.0 from 0.4.2. udibo/juniper and udibo/oauth2 map breaking changes to minor until their APIs stabilise, and this package now does the same.

Verification

• deno task check and deno task test pass in a standalone clone with this change (7 passed, 0 failed). Inside the udibo root checkout, the tailwindcss 4 test fails with "Config file must be a member of the workspace" whether or not this change is applied, because this package is not a root workspace member.
• Evidence the rule does what it says: the same rule in juniper and oauth2 turned feat!: and fix(react)!: commits into the minor releases 0.12.0, 0.15.0, 0.4.0, and 0.8.0.

Risk

Door: two-way. Release configuration only; a chore commit triggers no release. Moving to 1.0.0 later means changing this rule back to major.

Closes

Closes #14

🤖 Generated with Claude Code