chore(deps): bump detect-port from 1.6.1 to 2.1.0

[clemens]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Enabling PNPM's trustPolicy: no-downgrade setting throws warnings about detect-port version 1.6.1 (which Docusaurus uses), because 1.6.0 had provenance whereas 1.6.1 doesn't (which constitutes a downgrade). For 2.1.0, attestations are fine again:

While it would be possible to just whitelist that particular package and version, it seems worth it to me to actually upgrade the dependency:

• 1.6.1 is more than 2 years old, while 2.1.0 is at least a little younger (1.5 years)
• The breaking change in 2.0.0 was the removal of support for Node 16, which shouldn't affect Docusaurus due to its own limitation to Node 24.

Test Plan

Since no code was added/removed, I ran the tests and linters to avoid regressions.

Test links

Deploy preview: https://deploy-preview-12012--docusaurus-2.netlify.app/

Related issues/PRs

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​supports-color@​10.0.0
	@​types/​dedent@​0.7.2
	@​types/​github-slugger@​1.3.0
	@​types/​update-notifier@​6.0.8
	@​types/​buble@​0.20.5
	@​typescript-eslint/​parser@​5.62.0
	@​types/​prompts@​2.4.9
	@​vercel/​analytics@​1.3.1
	@​types/​rtlcss@​3.5.4
	@​types/​color@​3.0.6
	@​types/​js-yaml@​4.0.9
	@​types/​webpack-bundle-analyzer@​4.7.0
	@​types/​escape-html@​1.0.4
	@​types/​serve-handler@​6.1.4
	@​types/​file-loader@​5.0.4
	@​ai-sdk/​react@​2.0.133
	@​types/​webpack-env@​1.18.8
	@​argos-ci/​playwright@​2.0.0
	@​types/​picomatch@​2.3.4
	@​types/​semver@​7.7.1
	@​types/​micromatch@​4.0.10
	@​types/​react-dom@​19.2.3
	@​types/​shelljs@​0.8.15
	@​types/​fs-extra@​11.0.4
	@​philpl/​buble@​0.19.7
	@​types/​jest@​30.0.0
	@​typescript-eslint/​utils@​5.62.0
	react@​16.14.0
	@​typescript-eslint/​eslint-plugin@​5.62.0
	@​total-typescript/​shoehorn@​0.1.2
	@​types/​stringify-object@​3.3.1
	@​types/​nprogress@​0.2.3
	@​types/​lodash@​4.17.24
See 17 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm algoliasearch is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: packages/docusaurus-theme-search-algolia/package.json → npm/algoliasearch@5.51.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/algoliasearch@5.51.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm svgo is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/@svgr/webpack@8.1.0 → npm/svgo@3.3.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/svgo@3.3.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm tar is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@crowdin/cli@4.14.2 → npm/tar@7.5.13 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tar@7.5.13. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	2c14310
🔍 Latest deploy log	https://app.netlify.com/projects/docusaurus-2/deploys/6a031f60fe5f730008a8bade
😎 Deploy Preview	https://deploy-preview-12012--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.