Pin deploy workflow to Node 22.13.0 for pnpm/node:sqlite compatibility

[Copilot]

PR #48’s deploy workflow fails because the job runs on Node 20 while the toolchain now requires Node 22.13+ (pnpm runtime check and node:sqlite usage). This updates the deploy runtime to a compatible Node version in a targeted way.

• Workflow runtime update

  • Updated .github/workflows/deploy.yml to run actions/setup-node@v4 with node-version: '22.13.0' in the Deploy job.
  • No other workflow behavior was changed.

• Compatibility impact

  • Aligns deploy job runtime with current package/tooling expectations (including modern Node built-ins used by the installed pnpm stack).

- uses: actions/setup-node@v4
  with:
    node-version: '22.13.0'
    cache: 'pnpm'

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/RepoFuse/RepoFuse/node_modules/.bin/../next/dist/bin/next build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Fix the failing CI/deploy workflow for PR #48 in DealPatrol/RepoFuse.

Context:

• The failing job is job ID 77317981525 from the "Deploy to Vercel" workflow.
• The failure log shows:
  • Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite
  • This version of pnpm requires at least Node.js v22.13
  • The job was running Node.js v20.20.2
• The workflow file is .github/workflows/deploy.yml.
• In that workflow, actions/setup-node@v4 is configured with node-version: '20'.
• The repo's package.json also suggests modern Node usage (@types/node is ^22).

Task:

• Update the workflow so the deploy job runs on a compatible Node version that satisfies pnpm and supports node:sqlite.
• Keep the fix minimal and targeted.
• Ensure the workflow remains valid GitHub Actions YAML.
• Create a pull request with the change.

Relevant file:

• .github/workflows/deploy.yml

Suggested fix direction:

• Change node-version from 20 to 22 (or an explicit compatible 22.x version if appropriate).

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Please find a solution for failing job 77317981525. Use the logs, job definition, and any referenced files where the failure occurred. Keep your response focused on the solution and include code suggestions when appropriate.

Assistant: The failure is caused by a Node version mismatch in the deploy workflow.

Root cause

The job runs Node 20 in the workflow, but the build uses tooling that now requires Node 22.13+:

• Workflow sets node-version: '20' in .github/workflows/deploy.yml:24-27
• Logs show:
  • pnpm requires at least Node.js v22.13
  • Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite

node:sqlite is only available in newer Node versions, so the deploy job fails before the app can build.

Fix

Update the workflow to use Node 22 instead of Node 20.

Suggested change

In deploy.yml, change:

- uses: actions/setup-node@v4
  with:
    node-version: '20'
    cache: 'pnpm'

to:

- uses: actions/setup-node@v4
  with:
    node-version: '22'
    cache: 'pnpm'

If you want to be explicit about the minimum supported version from the logs, use:

- uses: actions/setup-node@v4
  with:
    node-version: '22.13.0'
    cache: 'pnpm'

Why this is the right fix

Your repo is already aligned with newer Node tooling:

• @types/node is ^22 in package.json
• Current dependencies include modern Next/Vercel tooling that can pull in newer runtime expectations

Recommended patch

diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
@@
       - uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version: '22'
           cache: 'pnpm'

Summary

Use Node 22 in the deploy job. That resolves both the pnpm version requirement and the missing node:sqlite builtin module error.

User: Please make the changes for me

Assistant: I’m waiting for your approval of the proposed repository change so I can continue and create the PR with the workflow fix.

This pull request was created from Copilot chat.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
repo-app-architect	Ready	Preview, Comment	May 23, 2026 10:51pm
repofuse	Ready	Preview, Comment, Open in v0	May 23, 2026 10:51pm
v0-repo-app-architect	Ready	Preview, Comment, Open in v0	May 23, 2026 10:51pm

[supabase]

This pull request has been ignored for the connected project bpjftwoiosftvjvxpovz because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.