ci: add update-pnpm action

[btea]

Description

Refer to https://github.com/nodejs/nodejs.org/blob/main/.github/workflows/pnpm-updater.yml
#1093 (review)

Validation

Related Issues

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run node --run test and all tests passed.
• I have check code formatting with node --run format:check & node --run lint.
• I've covered new added functionality with unit tests if necessary.

[vercel]

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

Project	Deployment	Actions	Updated
api-docs-tooling	Ready	Preview	Oct 5, 2026 6:57am UTC

[github-actions]

api-links Generator

Performance estimate _{(single CI run)}

• Generation time: 1.1% faster (930.00 ms → 920.00 ms)
• Peak memory: 0.1% lower (440.48 MB → 440.04 MB)

json Generator

Performance estimate _{(single CI run)}

• Generation time: 29.4% slower (6.90 s → 8.93 s)
• Peak memory: 0.9% higher (1.58 GB → 1.60 GB)

legacy-html Generator

Performance estimate _{(single CI run)}

• Generation time: 3.6% slower (41.47 s → 42.96 s)
• Peak memory: 2.2% higher (2.41 GB → 2.46 GB)

legacy-json Generator

Performance estimate _{(single CI run)}

• Generation time: 24.0% faster (8.71 s → 6.62 s)
• Peak memory: 6.2% higher (1.56 GB → 1.65 GB)

llms-txt Generator

Performance estimate _{(single CI run)}

• Generation time: 44.0% slower (4.93 s → 7.10 s)
• Peak memory: 10.6% lower (1.83 GB → 1.63 GB)

orama-db Generator

Output size: 1 file changed · net -141.00 B

File size details

File	Main	PR	Change
orama-db.json	9.54 MB	9.54 MB	-141.00 B (-0.0%)

Performance estimate _{(single CI run)}

• Generation time: 9.6% slower (4.99 s → 5.47 s)
• Peak memory: 7.6% lower (1.84 GB → 1.70 GB)

web Generator

Performance estimate _{(single CI run)}

• Generation time: 1.9% faster (64.65 s → 63.39 s)
• Peak memory: 0.2% higher (3.33 GB → 3.34 GB)

[MattIPv4]

Can we just introduce the action here, and let it do the version update? Let's avoid making PRs non-atomic by introducing a major version update in the same PR as CI changes.

[btea]

Can we just introduce the action here, and let it do the version update? Let's avoid making PRs non-atomic by introducing a major version update in the same PR as CI changes.

Done.