Tracking issue for conventional-changelog preset updates

[travi]

My release workflow is broken with an error about conventional-changelog-*

new versions of conventional-changelog presets were released over the weekend with breaking changes. these updates were properly released as major versions, but you may be installing the latest version as part of your release pipeline.

Note: if you are using the default angular preset through the core package without installing independently, you should not be experiencing problems because the previous major is still defined as the installed dependency in that situation

What can i do to fix my release pipeline?

you will need to specify a version or version range for the preset package that you are installing. for example, if you are installing with npm before executing, you could update like:

- npm install -g semantic-release conventional-changelog-conventionalcommits
+ npm install -g semantic-release conventional-changelog-conventionalcommits@6

What will the semantic-release team do to handle this issue going forward?

this is a breaking change for us too. this is a change to how presets are loaded and we will be updating to handle the change. however, we want to make sure we handle the update properly, so we are not making the change immediately. we will likely treat this change as a breaking change for our consumers by dropping support for loading the presets that used the previous loading approach.

Other issues exposed by this situation

we are seeing feedback about some other issues that need attention that arent directly related to this issue, but are exposed/highlighted by this situation. we are paying attention to that feedback, but will need to follow up on those issues after the primary complications are addressed.

• Tracking issue for errors resulting in a zero exit code #2932

How can i help?

if you are looking to resolve problems with your releases, focus on specifying the version of the preset you are loading. however, if you would like to help us investigate these issues, we welcome you help and participation in the conversation.

[vytautas-pranskunas-]

watching

[vitorf7]

Ahh let me check my company's GitHub actions workflows to see if this fixes the reason why all of a sudden our flows stopped creating new tags and releases

[travi]

a new beta version is available as a result of this wip pr: #2934

we would appreciate if folks that are impacted by this change would give the beta a try to help give us confidence that we've fully handled the changes. install with npm install semantic-release@beta or use with npx as npx semantic-release@beta.

[marksie1988]

Just tested with the beta and this has fixed it for me 👍 thanks for that.

[jmarrio1]

I can confirm also confirm that using beta release fixes this issue for us! Thanks @travi

[fin-gal]

Using beta also solved the problem on my side, thank you so much!

[github-actions]

🎉 This issue has been resolved in version 22.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀