refactor: Bump npm from 11.20.0 to 11.21.1

[mtrezza]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.

Issue

Resolves the security advisories of the dependencies bundled in npm 11.20.0 for the development dependency tree (release tooling):

• brace-expansion 5.0.9: GHSA-q2hr-2g5m-vwhr (medium, fixed in 5.0.12; https://github.com/parse-community/parse-dashboard/security/dependabot/460)
• ip-address 10.5.0: GHSA-j6r3-76f7-8jcv (medium, fixed in 10.7.1; https://github.com/parse-community/parse-dashboard/security/dependabot/463), GHSA-rpw4-54j3-4h4q (medium, fixed in 10.5.1; https://github.com/parse-community/parse-dashboard/security/dependabot/454) and GHSA-2vr4-cq9g-pvrc (medium, fixed in 10.5.1; https://github.com/parse-community/parse-dashboard/security/dependabot/453)
• postcss-selector-parser 7.1.4: GHSA-rj75-hqrm-r3gf (medium, fixed in 7.1.6; https://github.com/parse-community/parse-dashboard/security/dependabot/472)
• undici 6.28.0: GHSA-r53p-7pc4-xj5r (low, fixed in 6.28.1; https://github.com/parse-community/parse-dashboard/security/dependabot/457)

Approach

npm is required as npm ^11.6.2 by @semantic-release/npm 13.1.4, and as npm ^10.5.0 by @semantic-release/npm 11.0.3 inside @saithodev/semantic-release-backmerge 4.0.1. The scoped override added in #3477 resolves the latter to exactly 11.20.0, so both share one npm copy. Because the override pins that exact version, npm update npm alone keeps 11.20.0. Following the approach of #3477, this bumps the override to 11.21.1, so both continue to share one npm 11.21.1 copy:

"overrides": {
  "@saithodev/semantic-release-backmerge": {
    "npm": "11.21.1"
  }
}

• node_modules/npm: 11.20.0 → 11.21.1, with the bundled brace-expansion 5.0.12, ip-address 10.7.2, postcss-selector-parser 7.1.6 and undici 6.29.0
• The lock file changes are limited to node_modules/npm and its bundled dependencies.

Releases will publish with npm 11.21.1. The release workflow's @semantic-release/npm 13.1.4 runs npm whoami, npm publish, npm dist-tag and npm version through the root node_modules/.bin/npm.

Changes

• 11.21.0: npm dist-tag supports OIDC authentication (feat(dist-tag): support OIDC authentication npm/cli#10056); @npmcli/config 10.14.0
• 11.21.1: Fixed writing registry allowScripts keys with install-strategy=linked (fix: write registry allowScripts keys under install-strategy=linked npm/cli#10059); bundled dependency updates (brace-expansion 5.0.12, ip-address 10.7.2, postcss-selector-parser 7.1.6, undici 6.29.0, http-cache-semantics 4.3.0, @npmcli/arborist 9.9.3)

Breaking Changes

None. The OIDC token exchange in npm publish and npm dist-tag only runs when an OIDC ID token is available; the release workflow does not grant id-token: write, so both continue to authenticate with NPM_TOKEN. npm 11.21.1 supports Node ^20.17.0 || >=22.9.0, which includes the release workflow's Node 24.

Code Changes Required

None. The change is limited to the overrides entry in package.json and the lock file.

Tasks

No tasks apply; this PR only changes development dependency resolution.

Summary by CodeRabbit

• Chores
  • Updated the bundled npm tooling from version 11.20.0 to 11.21.1, along with its associated bundled components and package metadata.
  • No user-facing features or behavior changes are included in this update.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Essentials
• Run ID: ffef6659-ec7a-4d24-95ab-41975da972e1

📥 Commits

Reviewing files that changed from the base of the PR and between 3e689a7 and 9326ea5.

📒 Files selected for processing: 2

• package-lock.json
• package.json

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

📝 Walkthrough

The npm override changes from 11.20.0 to 11.21.1. The lockfile updates npm’s resolved package and integrity data, bundled dependency ranges, and selected bundled package versions.

Changes: npm Dependency Update

Layer / File(s)	Summary
Update npm override and bundled dependencies package.json, package-lock.json	The npm override and locked npm package update to 11.21.1. The lockfile also updates bundled dependency ranges and versions, including @npmcli/arborist, @npmcli/config, and several libnpm packages.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: semantic-release-bot

Merge Risk: ⚪ Minimal · up to 9326e

This updates the npm version used by release tooling. The supported Node versions meet its engine requirement, and no concrete merge-blocking issue remains.

Pre-merge checks: 7

Check name	Status	Explanation
Title check		The title begins with the allowed refactor: prefix and clearly describes the npm version update. The subject starts with a capital letter.
Description check		The description includes all required sections. It explains the security issue, approach, affected dependencies, release impact, breaking changes, code changes, and task status.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Security Check		PASS. The pull request changes only the npm override and lockfile dependency metadata. It introduces no application code, scripts, permissions, authentication changes, or unsafe URL changes. The lockf…
Engage In Review Feedback		PASS. The supplied review metadata reports zero actionable findings and no returned review threads. No review feedback required engagement, implementation, or discussion.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Full details: Security Check

Explanation

PASS. The pull request changes only the npm override and lockfile dependency metadata. It introduces no application code, scripts, permissions, authentication changes, or unsafe URL changes. The lockfile replaces the reported vulnerable bundled versions with npm 11.21.1 and updated versions of brace-expansion, ip-address, postcss-selector-parser, and undici. The npm package remains resolved from registry.npmjs.org with a recorded integrity hash, and the updated packages are marked as development dependencies.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}