Conversation
* fix(deps): update npm to v11 * feat(node-versions): drop support for node versions v20, v21, and v23 in accordance with our [Node Support Policy](https://semantic-release.gitbook.io/semantic-release/support/node-support-policy) BREAKING CHANGE: a minimum of node v22.14 is now required this is a step in resolving #966 * fix(deps): raise the minimum for the npm version range to account for the brace-expansion patch #966 (comment) for #966 --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Matt Travi <[email protected]>
|
🎉 This PR is included in version 13.0.0-alpha.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 13.0.0-beta.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 13.0.0-alpha.16 🎉 The release is available on: Your semantic-release bot 📦🚀 |
…he v24 range since v24 has not yet been promoted to LTS BREAKING CHANGE: the minimum node version for the v24 range is now v24.10.0
|
🎉 This PR is included in version 13.0.0-beta.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 13.0.0-beta.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
this doesnt include the solution for #958, but does the work to get the dependency on npm updated to a version that supports it. since doing that requires dropping support for old versions of node, this gets us past that step, which we're overdue for anyway. i think we should merge this as it is rather than waiting to batch it with #958. i dont expect the remainder of that work to run into any additional breaking changes that would prevent that work from being released as simply a new feature. |
the two changes are fairly independent, but both will need to get merged back into the alpha branch, which i'll take care of shortly |
|
🎉 This PR is included in version 13.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
changes
breaking changes