Skip to content

fix(deps): update npm to v11 #909

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Jun 24, 2025
Merged

fix(deps): update npm to v11 #909

merged 3 commits into from
Jun 24, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 16, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
npm (source) 10.9.2 -> 11.4.2 age adoption passing confidence
npm (source) ^10.5.0 -> ^11.0.0 age adoption passing confidence

Release Notes

npm/cli (npm)

v11.4.2

Compare Source

Bug Fixes
Documentation
Dependencies
Chores

v11.4.1

Compare Source

Documentation
Chores
Dependencies

v11.4.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies
Chores

v11.3.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies
Chores

v11.2.0

Compare Source

Features
Bug Fixes
Dependencies
Chores

v11.1.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies
Chores

v11.0.0

Compare Source

Documentation
Dependencies
Chores

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-11.x branch 3 times, most recently from cac7ac7 to 273437b Compare December 23, 2024 04:56
@renovate renovate bot force-pushed the renovate/npm-11.x branch 3 times, most recently from 20732de to ce0a603 Compare January 4, 2025 15:25
@renovate renovate bot force-pushed the renovate/npm-11.x branch 3 times, most recently from c28c3f8 to 642b5ce Compare January 11, 2025 22:17
@renovate renovate bot force-pushed the renovate/npm-11.x branch 4 times, most recently from 534dcdb to d975608 Compare January 20, 2025 04:34
@renovate renovate bot force-pushed the renovate/npm-11.x branch 3 times, most recently from b877f85 to 10f5108 Compare January 29, 2025 22:09
@renovate renovate bot force-pushed the renovate/npm-11.x branch 2 times, most recently from 4577206 to 2e2e2b1 Compare March 8, 2025 03:02
@renovate renovate bot force-pushed the renovate/npm-11.x branch 11 times, most recently from 21491e0 to 01b82a4 Compare April 7, 2025 12:59
@renovate renovate bot force-pushed the renovate/npm-11.x branch from 01b82a4 to d8dc9b2 Compare April 8, 2025 19:27
@renovate renovate bot force-pushed the renovate/npm-11.x branch 5 times, most recently from cd61318 to 674382e Compare May 26, 2025 06:09
@renovate renovate bot force-pushed the renovate/npm-11.x branch 4 times, most recently from af3e411 to 8087aaa Compare June 9, 2025 05:41
@renovate renovate bot force-pushed the renovate/npm-11.x branch 3 times, most recently from fa4f311 to 250ee53 Compare June 13, 2025 16:55
@renovate renovate bot force-pushed the renovate/npm-11.x branch from 250ee53 to 4ffd8c3 Compare June 16, 2025 05:31
@MikeMcC399 MikeMcC399 mentioned this pull request Jun 19, 2025
Closed
@travi travi changed the base branch from master to beta June 20, 2025 19:05
@travi
feat(node-versions): drop support for node versions v20, v21, and v23
82e834d 
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
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jun 20, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@travi
Copy link
Member

travi commented Jun 20, 2025

this should be merged with a normal merge rather than squashing. the commit that relates to changing supported node versions is breaking and unrelated to the npm upgrade other than meeting the required ranges to allow the upgrade

travi
travi reviewed Jun 20, 2025
View reviewed changes
package.json
@@ -50,7 +50,7 @@
"strip-ansi": "7.1.0"
},
"engines": {
"node": ">=20.8.1"
"node": "^22.14.0 || >= 24.2.0"
Copy link
Member

@travi travi Jun 20, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

i debated between this and >=22.14.0. i'm interested in feedback @semantic-release/maintainers

landed here because v23 is already EOL, so i'd prefer not to include it in the supported range. dropped v20 in accordance with our node support policy. this is a little bit awkward because of v24 not yet being LTS, so i made the minimum of the v24 range the most recent release instead of the first LTS version, like i normally would. we may want to raise this further if additional v24 releases happen before we promote this to stable.

for the v22 range, i matched the range i landed on for some of my other projects. i tried to remember why i landed on specifically 22.14 as the minimum there, but i havent tracked it down. however, this does account for the new requirements for yargs that we'll need to handle in semantic-release/semantic-release#3745

Copy link
Member

Choose a reason for hiding this comment

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

This looks good Matt.

Our Node support policy surely allows this with the mention of support for "LTS"; with a good bit of the "Current" and other supported versions in CI

The exact Node LTS version is v22.16.0 though; but is it alright to have v22.14.0 at min range?? 🤔

Copy link
Contributor

Choose a reason for hiding this comment

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

Node.js v22.17.0 is expected to release tomorrow June 24, 2025, if you want to be completely up-to-date on the Node.js 22.x release line

@travi travi requested a review from a team June 20, 2025 20:09
MikeMcC399
MikeMcC399 reviewed Jun 22, 2025
View reviewed changes
@gr2m gr2m merged commit debc7c5 into beta Jun 24, 2025
11 checks passed
@gr2m gr2m deleted the renovate/npm-11.x branch June 24, 2025 22:23
@github-actions GitHub Actions
Copy link

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

The release is available on:

Your semantic-release bot 📦🚀

@github-actions 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 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@travi travi travi left review comments

@babblebey babblebey babblebey left review comments

@MikeMcC399 MikeMcC399 MikeMcC399 left review comments

@gr2m gr2m gr2m approved these changes

Assignees
No one assigned
Labels
released on @alpha released on @beta
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@travi @gr2m @babblebey @MikeMcC399