chore(deps): update dependency get-port to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
get-port	^5.1.1 → ^7.2.0

---

Release Notes

sindresorhus/get-port (get-port)

v7.2.0

Compare Source

• Add reserve option to lock ports for the process lifetime 8af215b

---

v7.1.0

Compare Source

• Add clearLockedPorts() method (#​70) d4fb7f8

v7.0.0

Compare Source

Breaking

• Require Node.js 16 5cc3422

Improvements

• Use timeout instead of interval for releasing ports (#​68) bd8a403

v6.1.2

Compare Source

• Fix portNumbers argument validation and number generation (#​64) 1fb0e70

v6.1.1

Compare Source

• Mark package as side effect free (#​63) d7ba424

v6.1.0

Compare Source

• Add exclude option (#​53) d03c07b

v6.0.0

Compare Source

Breaking

• Require Node.js 12.20 c08a4ae
• This package is now pure ESM. Please read this.
• require('get-port').makeRange => import {portsNumbers] from 'get-port'

Improvements

• Check all local hosts for port availability (#​56) c3bbed9

---

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 and 15 of the month (* 0-3 1,15 * *)
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

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

---

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The get-port package listed under devDependencies in package.json for @rspack/plugin-test has its version constraint updated from ^5.1.1 to ^7.2.0. No other files are modified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title accurately describes the main change: updating the get-port dependency from v5 to v7.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description accurately matches the dependency bump of get-port from ^5.1.1 to ^7.2.0.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/get-port-7.x

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 38: The package.json file is missing an explicit Node engine constraint
even though the newly added [email protected] dependency requires Node >=16. Add
"node": ">=16" to the engines field in package.json to declare this minimum Node
version requirement and prevent unsupported local installations.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0e6d601b-5cdc-475c-9695-683614bd984b

📥 Commits

Reviewing files that changed from the base of the PR and between 68ae1f0 and 36b26d3.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Node/pnpm engine declarations =="
fd -HI 'package.json|.nvmrc|.node-version|.tool-versions' | while read -r f; do
  echo "--- $f"
  sed -n '1,220p' "$f"
done

echo
echo "== CI/workflow node-version references =="
rg -n -C2 'node-version|setup-node|actions/setup-node|NODE_VERSION' .github/workflows || true

echo
echo "== get-port usage patterns that may be impacted by v6+ API changes =="
rg -n -C3 --type=js --type=ts --type=mjs --type=cjs 'get-port|makeRange|portNumbers|clearLockedPorts|reserve'

Repository: rstackjs/rspack-plugin-ci

Length of output: 17103

---

🏁 Script executed:

cat .github/workflows/test.yml

Repository: rstackjs/rspack-plugin-ci

Length of output: 1466

---

🏁 Script executed:

rg -n 'matrix|node' .github/workflows/test.yml | head -20

Repository: rstackjs/rspack-plugin-ci

Length of output: 412

---

Add explicit Node engine constraint to match [email protected] requirement.

[email protected] requires Node >=16, but package.json does not declare a Node engine floor—only pnpm version is constrained. While CI tests only Node 22.x (which satisfies the requirement), the missing constraint leaves a gap where local installs could use unsupported versions. Add "node": ">=16" to the engines field for clarity and to prevent version mismatches.

Note: get-port is not directly used in the codebase, so the risk of breaking changes from the v5→v7 upgrade is low.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 38, The package.json file is missing an explicit Node
engine constraint even though the newly added [email protected] dependency requires
Node >=16. Add "node": ">=16" to the engines field in package.json to declare
this minimum Node version requirement and prevent unsupported local
installations.