fix(bump): also propagate the parserOpts from args to conventionalRecommendedBump - #89
Conversation
|
Just thought about test and ran the existing tests locally. Fixing the mock function, since the PR adds the third function parameter to 'conventional-recommended-bump'. I'll also have a look at the tests and what I could add for the parserOpts propagation. |
… the mocking for tests
|
updated the tests / mocking. |
|
@TimothyJones do you have some time by any chance to look at this PR at some point? :) |
|
Apologies, I was away when this came in. I’ll take a look at this in the next 24 hours |
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## master #89 +/- ##
=======================================
Coverage 97.57% 97.57%
=======================================
Files 31 31
Lines 1280 1280
=======================================
Hits 1249 1249
Misses 31 31
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
no worries (was just checking if it might have been overlooked) :) thank you |
Hi, to resolve the following behaviour (raised in the deprecated origin: conventional-changelog/standard-version#690 (comment)) I've taken the idea and change of an already opened pull request conventional-changelog/standard-version#821 (also from the deprecated origin) to fix it.
The bug thats observed is that when using the
parserOptsand settingheaderPatternto for example match the Azure DevOps prefix e.g using this regex"(?:\\(Merged PR \\d+: \\))?([a-zA-Z]+)(?:\\(([\\w$\\.\\-*\\s]*)\\))?\\!?:(.*)"features committed with e.g. "feat: abc" and then merged as "Merged PR 0: feat: abc" are classified correctly when writing them to the changelog but the bump only increases the patch. Thats the default bump. The bump uses the default config and the parserOpts seem not to be propagated.parserOpts(andwriterOpts) were added but only for the changelog lifecycle, as far as I can see: #37Any concerns about this fix? :)