Skip to content

🔧 (repo) [NO-ISSUE]: Update toolchain#1570

Closed
ldg-github-ci wants to merge 0 commit into
developfrom
chore/no-issue-update-toolchain
Closed

🔧 (repo) [NO-ISSUE]: Update toolchain#1570
ldg-github-ci wants to merge 0 commit into
developfrom
chore/no-issue-update-toolchain

Conversation

@ldg-github-ci

Copy link
Copy Markdown
Contributor

This PR updates the toolchain (node, npm, pnpm) to the newest versions and deduplicates packages

@ldg-github-ci
ldg-github-ci requested a review from a team as a code owner June 21, 2026 01:20
Copilot AI review requested due to automatic review settings June 21, 2026 01:20
@vercel

vercel Bot commented Jun 21, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
device-sdk-ts-sample Ready Ready Preview, Comment Jun 21, 2026 1:23am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
doc-device-management-kit Ignored Ignored Jun 21, 2026 1:23am

Request Review

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the repository toolchain versions (via proto) and refreshes the dependency lockfile as part of a “toolchain update + dedupe” automation flow.

Changes:

  • Bumped pinned tool versions in .prototools (node/npm/pnpm).
  • Regenerated pnpm-lock.yaml, updating dependency resolutions and recording new deprecation metadata from upstream packages.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 6 comments.

File Description
.prototools Updates pinned toolchain versions used by CI/local setup via proto use.
pnpm-lock.yaml Refreshes the dependency graph and captures updated resolutions/deprecation metadata after toolchain/dedupe.
Files not reviewed (1)
  • pnpm-lock.yaml: Generated file

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .prototools Outdated
Comment on lines +1 to +3
node = "20.20.2"
npm = "11.17.0"
pnpm = "10.34.4"
Comment thread pnpm-lock.yaml Outdated
Comment on lines +516 to +524
ts-node:
specifier: 'catalog:'
version: 10.9.2(@types/node@24.3.0)(typescript@5.9.2)
version: 10.9.2(@types/node@22.10.1)(typescript@5.9.2)
tsx:
specifier: 'catalog:'
version: 4.19.2
vitest:
specifier: 'catalog:'
version: 3.2.4(@types/debug@4.1.12)(@types/node@24.3.0)(jiti@1.21.6)(jsdom@26.0.0(bufferutil@4.0.9)(utf-8-validate@5.0.10))(terser@5.43.1)(tsx@4.19.2)(yaml@2.7.0)
version: 3.2.4(@types/debug@4.1.12)(@types/node@22.10.1)(jiti@1.21.6)(jsdom@26.0.0(bufferutil@4.0.9)(utf-8-validate@5.0.10))(terser@5.43.1)(tsx@4.19.2)(yaml@2.7.0)
Comment thread pnpm-lock.yaml Outdated
Comment on lines +6305 to +6307
'@ungap/structured-clone@1.2.0':
resolution: {integrity: sha512-zuVdFrMJiuCDQUMCzQaD6KL28MjnqqN8XnAqiEq9PNm/hCPTSGfrXCOfwj1ow4LFb/tNymJPwsNbVePc1xFqrQ==}
deprecated: Potential CWE-502 - Update to 1.3.1 or higher
Comment thread pnpm-lock.yaml Outdated
Comment on lines +6429 to +6432
'@xmldom/xmldom@0.8.11':
resolution: {integrity: sha512-cQzWCtO6C8TQiYl1ruKNn2U6Ao4o4WBBcbL61yJl84x+j5sOWWFU9X7DpND8XZG3daDppSsigMdfAIl2upQBRw==}
engines: {node: '>=10.0.0'}
deprecated: this version has critical issues, please update to the latest version
Comment thread pnpm-lock.yaml Outdated
Comment on lines +6844 to +6847
basic-ftp@5.0.4:
resolution: {integrity: sha512-8PzkB0arJFV4jJWSGOYR+OEic6aeKMu/osRhBULN6RY0ykby6LKhbmuQ5ublvaas5BOwboah5D87nrHyuh8PPA==}
engines: {node: '>=10.0.0'}
deprecated: Security vulnerability fixed in 5.2.1, please upgrade
Comment thread pnpm-lock.yaml Outdated
Comment on lines +12735 to +12742
uuid@8.3.2:
resolution: {integrity: sha512-+NYs2QeMWy+GWFOEm9xnn6HCDp0l7QBD7ml8zLUmJ+93Q5NF0NocErnwkTkXVFNiX3/fpC6afS8Dhb/gz7R7eg==}
deprecated: uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).
hasBin: true

uuid@9.0.1:
resolution: {integrity: sha512-b+1eJOlsR9K8HJpow9Ok3fiWOWSIcIzXodvv0rQjVoOVNpWMpxf1wZNpt4y9h10odCNrqnYp1OBzRktckBe3sA==}
deprecated: uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).
@github-actions

Copy link
Copy Markdown
Contributor

Danger Check Results

Messages

⚠️

No changeset file found. Please make sure this is intended or add a changeset file.

Danger: All checks passed successfully! 🎉

Generated by 🚫 dangerJS against 482ed96

@sonarqubecloud

Copy link
Copy Markdown

@github-actions github-actions Bot closed this Jun 28, 2026
@github-actions
github-actions Bot force-pushed the chore/no-issue-update-toolchain branch from 482ed96 to 9cffe79 Compare June 28, 2026 01:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants