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
[semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: Merged PR 1135: PR with no description
[semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is patch
semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: Merged PR 1134: Another PR
With a description
[semantic-release] [@semantic-release/commit-analyzer] › ℹ The commit should not trigger a release
[semantic-release] [@semantic-release/commit-analyzer] › ℹ Analysis of 2 commits complete: patch release
Workaround
Issue #339 has a workaround, which is to specify one rule without a subject, message, tag or type:
This works with and without PR descriptions present, however commits starting with feat: no longer increment the minor version:
[semantic-release] [@semantic-release/commit-analyzer] › ℹ Analyzing commit: feat: Another PR
[semantic-release] [@semantic-release/commit-analyzer] › ℹ The release type for the commit is patch
[semantic-release] [@semantic-release/commit-analyzer] › ℹ Analysis of 1 commits complete: patch release
Hi all, my intention is to release a new patch version when the commit message doesn't start with
fix:
orfeat:
.These custom
releaseRules
work, except when the PR contains a description. PRs are created using Azure DevOps.package.json
Pipeline logs
Workaround
Issue #339 has a workaround, which is to specify one rule without a
subject
,message
,tag
ortype
:This works with and without PR descriptions present, however commits starting with
feat:
no longer increment the minor version:Package Versions
The text was updated successfully, but these errors were encountered: