-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails with latest semantic-release versions #103
Labels
Comments
Sounds good! Please submit a PR 😁 |
Saeger
added a commit
to Saeger/semantic-release-slack-bot
that referenced
this issue
Feb 9, 2023
BREAKING CHANGE: . fix juliuscc#103
PR opened |
Saeger
added a commit
to Saeger/semantic-release-slack-bot
that referenced
this issue
Feb 9, 2023
BREAKING CHANGE: . fix juliuscc#103
Saeger
added a commit
to Saeger/semantic-release-slack-bot
that referenced
this issue
Feb 9, 2023
BREAKING CHANGE: . fix juliuscc#103
Saeger
added a commit
to Saeger/semantic-release-slack-bot
that referenced
this issue
Feb 9, 2023
BREAKING CHANGE: . fix juliuscc#103
juliuscc
pushed a commit
that referenced
this issue
Mar 2, 2023
This PR proposes the bump of such version and allow our users to be able to include and use the latest version of semantic-release library and it's features in their applications. fixes #103 BREAKING CHANGE: We only support v18+ of Node and v20+ of semantic-release now. semantic-release library introduced a new version v20 which introduces several breaking changes, including but not limited Node v18 as requirement. More information can be found [here](https://github.com/semantic-release/semantic-release/releases/tag/v20.0.0).
🎉 This issue has been resolved in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This library's
peerDependencies
needs to be updated to support the latest semantic release version:20.1.0
. It currently fails to install on Node 18.The text was updated successfully, but these errors were encountered: