parserOpts not always passed to conventional-commits-parser about conventional-changelog

[thet]

I also found out that my original problem described in release-it/release-it#833 could be solved by using the config option ignoreRecommendedBump as described here: https://github.com/release-it/conventional-changelog#ignorerecommendedbump

However, there seems to be a problem with passing options to conventional-commits-parser.

Also, I might have overlooked the docs for breaking changes but it was only clear to me how a major release is detected after reading the source code. But that's a different problem.

[webpro]

I'm a bit surprised it gets there three times and that the second time the config is being applied.

Looking at this plugin's code, it makes sense it's applied only once:

conventional-changelog/index.js

Lines 73 to 76 in 20bf5dc

	delete options.context;
	delete options.gitRawCommitsOpts;
	delete options.parserOpts;
	delete options.writerOpts;

Any chance you could do a run without those 4 lines of code, and see whether the options are applied every time? I'm happy to remove them if conventional-changelog ignores them on the first options argument.

[webpro]

You may also have been bitten by #38 (which was just fixed in the latest release-it)

[webpro]

Closing this as I think it's fixed. Feel free to open another ticket, though.