Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Feb 3, 2026

The repository uses pnpm's workspace:* protocol for internal dependencies, but CI workflows were configured for npm, which doesn't support this protocol. This caused npm ci to fail with Unsupported URL Type "workspace:".

Changes

Package manager configuration:

  • Add pnpm-workspace.yaml and pnpm-lock.yaml
  • Remove package-lock.json
  • Add packageManager: "pnpm@10.28.2" to package.json

CI workflows (.github/workflows/):

  • Enable Corepack before Node.js setup
  • Change cache from npm to pnpm
  • Replace npm cipnpm install --frozen-lockfile
  • Replace npm runpnpm run

Updated workflows: ci.yml, publish.yml, release.yml, azure-functions.yml

Documentation:

  • Update README.md and CONTRIBUTING.md to use pnpm commands

Example workspace dependency

{
  "dependencies": {
    "@plures/praxis-core": "workspace:*"
  }
}

This syntax requires pnpm; npm treats it as an invalid protocol.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI and others added 4 commits February 3, 2026 02:17
- Add pnpm-workspace.yaml configuration
- Generate pnpm-lock.yaml
- Remove package-lock.json (npm is incompatible with workspace: protocol)
- Add packageManager field to package.json specifying pnpm@10.28.2
- Update CI workflow to use pnpm with Corepack
- Enable Corepack in CI before setup-node
- Change cache from 'npm' to 'pnpm'
- Replace npm commands with pnpm equivalents

Co-authored-by: kayodebristol <3579196+kayodebristol@users.noreply.github.com>
- Update publish.yml to use pnpm for npm publishing
- Update release.yml to use pnpm for building and testing
- Update azure-functions.yml to use pnpm for Azure deployments
- Add Corepack enablement and pnpm cache to all workflows

Co-authored-by: kayodebristol <3579196+kayodebristol@users.noreply.github.com>
- Replace npm install/run/test commands with pnpm equivalents
- Update development setup instructions
- Update example running instructions
- Update dogfooding workflow documentation

Co-authored-by: kayodebristol <3579196+kayodebristol@users.noreply.github.com>
Remove unsafe --no-git-checks flag that bypasses git repository validation during publishing.

Co-authored-by: kayodebristol <3579196+kayodebristol@users.noreply.github.com>
Copilot AI changed the title [WIP] Update actions/upload-artifact from version 4 to 6 Fix CI failure: migrate from npm to pnpm workspace Feb 3, 2026
Copilot AI requested a review from kayodebristol February 3, 2026 02:23
@kayodebristol
Copy link
Contributor

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.

Copy link
Contributor Author

Copilot AI commented Feb 3, 2026

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 work is complete:

✅ Root cause fixed: migrated from npm to pnpm (commits 1483cf6-a0a4547)
✅ All CI workflows updated (.github/workflows/)
✅ Documentation updated (README.md, CONTRIBUTING.md)
✅ Tested locally: build, test, and scan:rules all pass
✅ Code review and security scan completed

The changes fix the CI failure on the base branch where npm ci failed due to pnpm's workspace:* protocol. This is a stacked PR on the dependabot branch, so CI won't run automatically, but the fixes are verified locally and ready for merge.

@kayodebristol
Copy link
Contributor

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.

@kayodebristol
Copy link
Contributor

This PR is currently Draft.

Minimal next steps:

  • Mark as Ready for review when safe
  • Ensure CI is green
  • Request review / address feedback

Once checks are green + required reviews are satisfied, we can squash merge.

@kayodebristol
Copy link
Contributor

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.

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