Upgrade to node LTS version (v16) base image in Dockerfile #173
Labels
Comments
codfish
added a commit
that referenced
this issue
Aug 8, 2022
codfish
added a commit
that referenced
this issue
Aug 9, 2022
Closes #173 BREAKING CHANGE: Runs using nodejs v18.x and npm v8 now, so any dependencies specified in extends or additional_packages that have dependency conflicts with semantic-release v19.x will cause the action to fail.
codfish
added a commit
that referenced
this issue
Aug 9, 2022
Closes #173 BREAKING CHANGE: Runs using nodejs v18.x and npm v8 now, so any dependencies specified in extends or additional_packages that have dependency conflicts with semantic-release v19.x will cause the action to fail.
codfish
added a commit
that referenced
this issue
Aug 9, 2022
Closes #173 BREAKING CHANGE: Runs using nodejs v18.x and npm v8 now, so any dependencies specified in extends or additional_packages that have dependency conflicts with semantic-release v19.x will cause the action to fail.
codfish
added a commit
that referenced
this issue
Aug 9, 2022
Closes #173 BREAKING CHANGE: Runs using nodejs v18.x and npm v8 now, so any dependencies specified in extends or additional_packages that have dependency conflicts with semantic-release v19.x will cause the action to fail.
|
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of today, v14 is in Maintenance mode and v16 is the active LTS version.
https://nodejs.org/en/about/releases/
Is there a reason you use v12 in the Docker image? Would you mind to bump to v16?
The text was updated successfully, but these errors were encountered: