Fix Node 18.x CI failure by migrating to pnpm #151
Conversation
- Add pnpm-workspace.yaml for workspace configuration - Generate pnpm-lock.yaml to replace package-lock.json - Update ci.yml to use pnpm with proper setup order - Update publish.yml to use pnpm for NPM publishing - Update release.yml to use pnpm for builds and tests - Update azure-functions.yml to use pnpm for deployments This fixes the EUNSUPPORTEDPROTOCOL error that occurred because the repo uses workspace:* protocol which is pnpm-specific. Co-authored-by: kayodebristol <3579196+kayodebristol@users.noreply.github.com>
Co-authored-by: kayodebristol <3579196+kayodebristol@users.noreply.github.com>
|
Draft PR noted by automated sweep. If this is ready, mark it Ready for review; otherwise please add the remaining checklist items/blockers. [@copilot] can help finalize when ready. |
This PR is ready for review. All changes are complete: ✅ Fixed Node 18.x CI failure by migrating from npm to pnpm (commits c998304, 3916561) The fix addresses the |
|
This PR is currently Draft.\n\nMinimal next steps:\n- Mark as Ready for review when safe\n- Ensure CI is green\n- Request review / address feedback\n\nOnce checks are green + required reviews are satisfied, we can squash merge. |
|
This PR is currently Draft. Minimal next steps:
Once checks are green + required reviews are satisfied, we can squash merge. |
|
Closing as superseded by #155 (single consolidated fix for the Node 18/20 CI + workspace:* issue). If we need to resurrect any approach from this PR, we can reopen. |
CI fails on Node 18.x with
EUNSUPPORTEDPROTOCOLerror because the repo usesworkspace:*protocol in package dependencies—a pnpm-specific syntax unsupported by npm.Changes
pnpm-workspace.yamldefining workspace packagespnpm-lock.yaml, removedpackage-lock.jsonci.yml- Setup pnpm before Node.js for proper cachingpublish.yml- Usepnpm publish --no-git-checksrelease.yml- Build and test with pnpmazure-functions.yml- Install deps with--productionflagAll workflows now use
pnpm/action-setup@v4precedingactions/setup-node@v6to ensure pnpm is available before cache initialization.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.