Skip to content

Comments

promote to stable#976

Merged
travi merged 4 commits intomasterfrom
beta
Oct 13, 2025
Merged

promote to stable#976
travi merged 4 commits intomasterfrom
beta

Conversation

@travi
Copy link
Member

@travi travi commented Jul 3, 2025

changes

breaking changes

  • a minimum of node v22.14 is now required

* 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]>
@github-actions
Copy link

github-actions bot commented Jul 9, 2025

🎉 This PR is included in version 13.0.0-alpha.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 13.0.0-beta.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 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
@github-actions
Copy link

🎉 This PR is included in version 13.0.0-beta.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 13.0.0-beta.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@travi travi marked this pull request as ready for review October 13, 2025 20:28
@travi
Copy link
Member Author

travi commented Oct 13, 2025

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.

@travi
Copy link
Member Author

travi commented Oct 13, 2025

when we do merge this, we should avoid squashing the commits to keep the granular detail of the changes included in this release

@travi travi requested a review from a team October 13, 2025 20:35
Copy link
Member

@babblebey babblebey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

This I assume will follow after we merge #1013 🤔

@travi
Copy link
Member Author

travi commented Oct 13, 2025

This I assume will follow after we merge #1013 🤔

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

@travi travi merged commit a71fe44 into master Oct 13, 2025
7 checks passed
@travi travi deleted the beta branch October 13, 2025 21:12
@github-actions
Copy link

🎉 This PR is included in version 13.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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants