Files
Anso b731258314 ci: keep pre-1.0 features on the patch line (#2185)
* ci: keep pre-1.0 features on the patch line

release-please now treats a feat commit as a patch bump while the version is
below 1.0.0, so compatible work ships in the next 0.98.N release and only an
approved version transition moves the minor or major digit.

A new pull request check detects the markers release-please reads as a version
transition and requires the version-transition-approved label. The release PR
is judged by its proposed manifest against origin/main, so an accidental minor
or major step fails before it can merge.

CONTRIBUTING.md and the pull request template state the compatibility rules the
patch line depends on.

* ci: accept every version marker the release parser reads

The marker scan only accepted a colon separator, so the " #" forms of the
BREAKING CHANGE, BREAKING-CHANGE and Release-As footers passed the pull request
gate even though release-please bumps the version for them. Accept ":" and " #",
the two separators the bundled parser defines, and match the type text it
accepts before the bang.

The release pull request decision now applies the patch line only while the base
manifest is below 1.0.0, so a feature release above 1.0 passes without the
transition label. The step into 1.0 and any later major move stay a maintainer
decision, and an unreadable manifest still fails closed.
2026-10-24 13:01:28 -04:00
..