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
v10 includes breaking changes. since it was released only days ago, we have not even evaluated what needs to be updated here to be compatible with the latest release. between those breaking changes and the fact that supported node versions are now restricted beyond our current support range, updating our support will not be able to happen until we release a new major version, which will not happen automatically.
please do not assume that updating to new major versions of companion dependencies is safe. you are responsible for ensuring compatibility of the plugins you use with semantic-release
I know v10 has breaking changes, I just thought to open the issue for transparency.
One question, though, about:
please do not assume that updating to new major versions of companion dependencies is safe. you are responsible for ensuring compatibility of the plugins you use with semantic-release
Isn't conventionalcommits a supported plugin for semantic-release? Since this dependency is used on these repositories, how are we responsible for compatibility? Is there some other plugin that semantic-release supports instead?
Isn't conventionalcommits a supported plugin for semantic-release? Since this dependency is used on these repositories, how are we responsible for compatibility?
you might be flirting with the line between compatible and supported with this question. this plugin is not maintained by this project. the timing of its release is not coordinated with our team. our plugin system supports the interface defined by the conventional-changelog presets. when breaking changes are made to that series of presets, the interface changes and our project needs to react to account for those breaking interface changes. because the interface changed, that means that the interface of our plugin system must also change to support the new interface. that means breaking changes for us. we will work through that process, but it is not immediate.
Is there some other plugin that semantic-release supports instead?
the preset you chose to use with your project is installed as a separate dependency. that means that you need to make sure that the version you have installed meets the interface expectations of our plugin system. if you want the compatibility to be guaranteed, we include the package for the angular preset by default, so that preset has better assurances to always be compatible (as long as it is not also installed separately, which can result in conflicts)
also keep in mind that the action you are using is also not supported by our team and is not our recommended approach for usage. if you want guidance for usage in the context of that action, please reach out to the team that maintains that action
It is valid that will l we will need to update our project to be compatible with the updated interface. However, we do not depend directly on this preset, so there is no update for us to perform specifically related to that. Your project is what depends on that package. For now, you need to downgrade to the previous major version.
Activity
travi commentedon Jul 1, 2026
v10 includes breaking changes. since it was released only days ago, we have not even evaluated what needs to be updated here to be compatible with the latest release. between those breaking changes and the fact that supported node versions are now restricted beyond our current support range, updating our support will not be able to happen until we release a new major version, which will not happen automatically.
please do not assume that updating to new major versions of companion dependencies is safe. you are responsible for ensuring compatibility of the plugins you use with semantic-release
vspallas-flyr commentedon Jul 3, 2026
Hi @travi, thanks for replying!
I know v10 has breaking changes, I just thought to open the issue for transparency.
One question, though, about:
Isn't
conventionalcommitsa supported plugin forsemantic-release? Since this dependency is used on these repositories, how are we responsible for compatibility? Is there some other plugin thatsemantic-releasesupports instead?travi commentedon Jul 3, 2026
you might be flirting with the line between compatible and supported with this question. this plugin is not maintained by this project. the timing of its release is not coordinated with our team. our plugin system supports the interface defined by the conventional-changelog presets. when breaking changes are made to that series of presets, the interface changes and our project needs to react to account for those breaking interface changes. because the interface changed, that means that the interface of our plugin system must also change to support the new interface. that means breaking changes for us. we will work through that process, but it is not immediate.
the preset you chose to use with your project is installed as a separate dependency. that means that you need to make sure that the version you have installed meets the interface expectations of our plugin system. if you want the compatibility to be guaranteed, we include the package for the angular preset by default, so that preset has better assurances to always be compatible (as long as it is not also installed separately, which can result in conflicts)
travi commentedon Jul 3, 2026
also keep in mind that the action you are using is also not supported by our team and is not our recommended approach for usage. if you want guidance for usage in the context of that action, please reach out to the team that maintains that action
vspallas-flyr commentedon Jul 3, 2026
I know. This is why I raised the issue to conventional-changelog (conventional-changelog/conventional-changelog#1494) in the first place, but I got redirected here.
Should I keep the issue open here, or is it not related at all for this repo?
travi commentedon Jul 3, 2026
It is valid that will l we will need to update our project to be compatible with the updated interface. However, we do not depend directly on this preset, so there is no update for us to perform specifically related to that. Your project is what depends on that package. For now, you need to downgrade to the previous major version.
travi commentedon Jul 4, 2026
same problem as semantic-release/release-notes-generator#992
chore(release): 3.65.2 [skip ci]
fix(deps): upgrade conventional changelog packages to latest major (#955
github-actions commentedon Aug 24, 2026
🎉 This issue has been resolved in version 14.0.0-beta.3 🎉
The release is available on:
Your semantic-release bot 📦🚀