Per the docs, previously I could force a version by adding Release-As: 0.2.0 somewhere in the body of the commit message used in the squash-merge to main regardless of other content in the message. Now it seems to only work if Release-As: 0.2.0 is not accompanied by other Github things like co-authors or perhaps just any presence of --- in the commit message.
Expected behavior
The GHA workflow run would create/update the release-please PR with the version provided in the Release-As: line.
TL;DR
Per the docs, previously I could force a version by adding
Release-As: 0.2.0
somewhere in the body of the commit message used in the squash-merge to main regardless of other content in the message. Now it seems to only work ifRelease-As: 0.2.0
is not accompanied by other Github things like co-authors or perhaps just any presence of---
in the commit message.Expected behavior
The GHA workflow run would create/update the release-please PR with the version provided in the
Release-As:
line.Observed behavior
It does not set the provided version.
Action YAML
Log output
Additional information
workflow: https://github.com/MxNxPx/quick-test/blob/main/.github/workflows/release-workflow.yaml
commits to main: https://github.com/MxNxPx/quick-test/commits/main/