chore: migrate from yarn to pnpm

[hanabi1224]

Summary of changes

Apply suggestions from https://pnpm.io/supply-chain-security

Changes introduced in this pull request:

Reference issue to close (if applicable)

Closes

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Outside contributions

• I have read and agree to the CONTRIBUTING document.
• I have read and agree to the AI Policy document. I understand that failure to comply with the guidelines will lead to rejection of the pull request.

Summary by CodeRabbit

• Chores

  • Migrated package manager from Yarn to PNPM across CI workflows, tasks, and project configs.
  • Set Node engine requirement to >=20 and added PNPM requirement >=10.
  • Bumped minor dependencies (prettier, docusaurus plugin) and removed Yarn packageManager entry.
  • Added PNPM workspace settings focused on supply-chain security.

• Documentation

  • Updated installation, build, and CI instructions to use PNPM and clarified docs wording.

[coderabbitai]

Walkthrough

Migrate repository from Yarn to pnpm: update GitHub Actions, docs, tooling configs, and package manifests to use pnpm commands; add pnpm/node engine declarations; add pnpm workspace settings and adjust dev dependencies and versions.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflows .github/workflows/docs-auto-update.yml, .github/workflows/docs-check.yml, .github/workflows/docs-deploy.yml	Replaced Yarn commands with pnpm equivalents (e.g., yarn --immutable → pnpm i --frozen-lockfile, yarn build → pnpm build, yarn md-fmt → pnpm md-fmt).
Top-level Manifests package.json, docs/package.json	Added engines entries for Node >=20 and pnpm >=10; removed packageManager: "yarn@..."; bumped prettier and small dependency/devDependency adjustments in docs/package.json.
Tooling & Tasks mise.toml	Replaced task commands from Yarn to pnpm; removed yarn tool, added node and pnpm tool declarations; updated task descriptions to reflect pnpm usage.
Docs & README docs/README.md	Replaced Yarn usage instructions and CI/dev commands with pnpm equivalents; minor wording edit.
PNPM Workspace Config docs/pnpm-workspace.yaml	Added pnpm workspace settings (blockExoticSubdeps: true, minimumReleaseAge: 1440) and supply-chain comment.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• chore(deps): bump prettier from 3.6.2 to 3.7.4 in /docs #6322: Updates prettier version in docs/package.json, overlapping dependency changes.
• chore(deps): bump deps in docs #5843: Adjusts @easyops-cn/docusaurus-search-local in docs/package.json, related to docs dependency updates.

Suggested labels

dependencies, javascript

Suggested reviewers

• akaladarshi
• LesnyRumcajs
• sudo-shashank

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'chore: migrate from yarn to pnpm' is directly aligned with the main objective of the changeset, which migrates all tooling and workflows from Yarn to pnpm across multiple files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch hm/prefer-pnpm-over-yarn

---

No actionable comments were generated in the recent review. 🎉

---

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