fix: remove duplicate pnpm version causing build-deploy failure

[Copilot]

pnpm/action-setup@v4 now errors when version is specified in the workflow and packageManager is set in package.json, since both pins must match exactly.

Changes

• .github/workflows/gh-pages.yml: Remove version: 9 from the pnpm/action-setup step — package.json already declares "packageManager": "pnpm@9.15.0", which the action reads automatically.

# Before
- uses: pnpm/action-setup@v4
  with:
    version: 9  # conflicts with packageManager field in package.json

# After
- uses: pnpm/action-setup@v4  # uses pnpm@9.15.0 from package.json

[cloudflare-workers-and-pages]

Deploying opensourcewin-github-io with    Cloudflare Pages

Latest commit:	e9385cb
Status:	✅  Deploy successful!
Preview URL:	https://57b70d1e.opensourcewin-github-io.pages.dev
Branch Preview URL:	https://copilot-fix-build-deploy-job.opensourcewin-github-io.pages.dev

View logs

[Copilot]

Pull request overview

Removes an explicit pnpm version pin in the GitHub Pages deployment workflow to avoid pnpm/action-setup@v4 failing when a packageManager version is already declared in package.json.

Changes:

• Removed the with: version: 9 configuration from the pnpm/action-setup@v4 step in the GitHub Pages workflow.
• Relies on the repository’s packageManager: "pnpm@9.15.0" declaration for consistent pnpm resolution.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.