You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using release-please-action with skip-github-pull-request: true on a main branch after a squash merge, no release is created despite the action completing successfully.
Expected behavior
I expected release-please-action to create a new release and update CHANGELOG.md and package.json with a new version after a PR titled with a Conventional Commit message was squash-merged into main.
Observed behavior
The action completed successfully but did not create a new release, nor did it update CHANGELOG.md or package.json. This occurred even though the squash-merged PR's title followed the Conventional Commits standard.
TL;DR
When using
release-please-action
withskip-github-pull-request: true
on amain
branch after a squash merge, no release is created despite the action completing successfully.Expected behavior
I expected
release-please-action
to create a new release and updateCHANGELOG.md
andpackage.json
with a new version after a PR titled with a Conventional Commit message was squash-merged intomain
.Observed behavior
The action completed successfully but did not create a new release, nor did it update
CHANGELOG.md
orpackage.json
. This occurred even though the squash-merged PR's title followed the Conventional Commits standard.Action YAML
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: