chore: switch workspace package manager to pnpm

[styfle]

Summary

• add pnpm workspace configuration with minimum release age and approved build scripts
• pin pnpm 10.33.0 via packageManager and replace Yarn commands in scripts/CI
• replace yarn.lock with pnpm-lock.yaml and update CI to Node 20
• make the test workspace depend on the local micro package via workspace:*

Testing

• source "$HOME/.nvm/nvm.sh" && nvm use 20 && pnpm install --frozen-lockfile && pnpm run test

  

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​node-fetch@​2.5.0 ⏵ 3.3.2	-1	+17
	npm/​lerna@​3.13.4 ⏵ 3.22.1			+1
	npm/​urlencoded-body-parser@​3.0.0
	npm/​openssl-self-signed-certificate@​1.1.6
	npm/​micro@​10.0.1
	npm/​socket.io@​1.7.3
	npm/​graphql-request@​7.4.0

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		Critical CVE: Insufficient validation when decoding a Socket.IO packet in npm socket.io-parser CVE: GHSA-qm95-pgcg-qqfq Insufficient validation when decoding a Socket.IO packet (CRITICAL) Affected versions: >= 4.0.0 < 4.0.5; >= 4.1.0 < 4.2.1; < 3.3.3; >= 3.4.0 < 3.4.2 Patched version: 3.3.3 From: ? → npm/socket.io@1.7.3 → npm/socket.io-parser@2.3.1 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/socket.io-parser@2.3.1. 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		High CVE: npm debug Inefficient Regular Expression Complexity vulnerability CVE: GHSA-9vvw-cc9w-f27h debug Inefficient Regular Expression Complexity vulnerability (HIGH) Affected versions: >= 3.0.0 < 3.1.0; < 2.6.9 Patched version: 2.6.9 From: ? → npm/socket.io@1.7.3 → npm/debug@2.2.0 ℹ Read more on: This package | This alert | What is a CVE? 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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/debug@2.2.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		High CVE: npm debug Inefficient Regular Expression Complexity vulnerability CVE: GHSA-9vvw-cc9w-f27h debug Inefficient Regular Expression Complexity vulnerability (HIGH) Affected versions: >= 3.0.0 < 3.1.0; < 2.6.9 Patched version: 2.6.9 From: ? → npm/socket.io@1.7.3 → npm/debug@2.3.3 ℹ Read more on: This package | This alert | What is a CVE? 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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/debug@2.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		High CVE: Resource exhaustion in npm engine.io CVE: GHSA-j4f2-536g-r55m Resource exhaustion in engine.io (HIGH) Affected versions: < 3.6.0 Patched version: 3.6.0 From: ? → npm/socket.io@1.7.3 → npm/engine.io@1.8.3 ℹ Read more on: This package | This alert | What is a CVE? 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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/engine.io@1.8.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		High CVE: Resource exhaustion in npm socket.io-parser CVE: GHSA-xfhh-g9f5-x4m4 Resource exhaustion in socket.io-parser (HIGH) Affected versions: = 3.4.0; < 3.3.2; >= 3.4.0 < 3.4.1 Patched version: 3.3.2 From: ? → npm/socket.io@1.7.3 → npm/socket.io-parser@2.3.1 ℹ Read more on: This package | This alert | What is a CVE? 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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/socket.io-parser@2.3.1. 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		High CVE: socket.io allows an unbounded number of binary attachments in npm socket.io-parser CVE: GHSA-677m-j7p3-52f9 socket.io allows an unbounded number of binary attachments (HIGH) Affected versions: < 3.3.5; >= 3.4.0 < 3.4.4; >= 4.0.0 < 4.2.6 Patched version: 3.3.5 From: ? → npm/socket.io@1.7.3 → npm/socket.io-parser@2.3.1 ℹ Read more on: This package | This alert | What is a CVE? 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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/socket.io-parser@2.3.1. 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		High CVE: Denial of Service in npm ws CVE: GHSA-5v72-xg48-5rpm Denial of Service in ws (HIGH) Affected versions: >= 0.2.6 < 1.1.5; >= 2.0.0 < 3.3.1 Patched version: 1.1.5 From: ? → npm/socket.io@1.7.3 → npm/ws@1.1.2 ℹ Read more on: This package | This alert | What is a CVE? 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: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ws@1.1.2. 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