docs: align README Node.js prerequisite with Node 24 upgrade

[mahata]

This PR completes follow-up cleanup from the Node 24 migration by removing the remaining outdated Node 22 prerequisite reference in docs. The goal is to keep setup guidance consistent across repository documentation.

• Documentation consistency

  • Updated the README prerequisite from Node.js v22+ to Node.js v24+ to match .node-version, workflow updates, and AGENTS.md.

• Change detail

  - Node.js (v22 or higher)
  + Node.js (v24 or higher)

[Copilot]

Pull request overview

Upgrades the repository’s Node.js version to 24 and removes Corepack-related configuration/steps from docs and GitHub Actions workflows.

Changes:

• Bump Node.js version from 22 to 24 via .node-version and update AGENTS.md.
• Remove corepack enable steps from CI/deploy/release workflows.
• Remove the packageManager field from package.json.

Show a summary per file

File	Description
package.json	Removes packageManager (previously used by Corepack) which impacts how pnpm version is pinned/discovered.
AGENTS.md	Updates documented Node version to 24.
.node-version	Updates Node major version to 24 for tooling/CI.
.github/workflows/ci.yml	Removes Corepack enable step; workflows still run pnpm commands.
.github/workflows/deploy.yml	Removes Corepack enable steps across jobs; workflows still run pnpm commands.
.github/workflows/electron-release.yml	Removes Corepack enable step; workflow still runs pnpm commands.

Copilot's findings

Comments suppressed due to low confidence (7)

.github/workflows/ci.yml:25

• actions/setup-node does not install pnpm; it only configures Node and can enable dependency caching. With the corepack enable step removed, pnpm install will fail unless pnpm is installed explicitly (e.g., via pnpm/action-setup or npm i -g pnpm@<pinned>).

This issue also appears on line 43 of the same file.

      - name: Setup Node.js
        uses: actions/setup-node@v5
        with:
          node-version-file: ".node-version"
          cache: "pnpm"
          cache-dependency-path: "pnpm-lock.yaml"

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

.github/workflows/ci.yml:52

• Same issue as the test job: after removing corepack enable, this job still runs pnpm ... but there is no step that installs pnpm. Add an explicit pnpm installation step before pnpm install.

      - name: Setup Node.js
        uses: actions/setup-node@v5
        with:
          node-version-file: ".node-version"
          cache: "pnpm"
          cache-dependency-path: "pnpm-lock.yaml"

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

.github/workflows/deploy.yml:30

• After removing corepack enable, this workflow still uses pnpm but does not install it anywhere. actions/setup-node caching does not provide pnpm itself, so CI will fail unless pnpm is installed explicitly (e.g., pnpm/action-setup or a global install of a pinned version).

This issue also appears in the following locations of the same file:

• line 48
• line 95

      - name: Setup Node.js
        uses: actions/setup-node@v5
        with:
          node-version-file: ".node-version"
          cache: "pnpm"
          cache-dependency-path: "pnpm-lock.yaml"

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

.github/workflows/deploy.yml:56

• This job also runs pnpm commands without installing pnpm (previously provided by corepack). Add an explicit pnpm installation step before pnpm install.

      - name: Setup Node.js
        uses: actions/setup-node@v5
        with:
          node-version-file: ".node-version"
          cache: "pnpm"
          cache-dependency-path: "pnpm-lock.yaml"

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

.github/workflows/deploy.yml:103

• The deploy job still uses pnpm but no longer enables corepack, and there is no other pnpm installation step. Ensure pnpm is installed (and ideally version-pinned) before running pnpm install and subsequent scripts.

      - name: Setup Node.js
        uses: actions/setup-node@v5
        with:
          node-version-file: ".node-version"
          cache: "pnpm"
          cache-dependency-path: "pnpm-lock.yaml"

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

.github/workflows/electron-release.yml:86

• With corepack enable removed, this workflow still relies on pnpm but does not install it. Add an explicit pnpm installation step (preferably pinned to the expected version) before pnpm install.

      - name: Setup Node.js
        uses: actions/setup-node@v5
        with:
          node-version-file: ".node-version"
          cache: "pnpm"
          cache-dependency-path: "pnpm-lock.yaml"

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

package.json:44

• Removing the packageManager field also removes the only machine-readable pin for the expected pnpm version. If corepack is no longer used, consider pinning pnpm in CI (and documenting how to install that version locally) to avoid drift and CI/local mismatches.

  ],
  "author": "",
  "license": "ISC",
  "pnpm": {
    "onlyBuiltDependencies": [
      "better-sqlite3",
      "electron",
      "esbuild",
      "workerd"
    ]
  },

• Files reviewed: 6/6 changed files
• Comments generated: 1

[Copilot]

Docs now say Node 24, but other docs in the repo still reference Node 22 in prerequisites. To avoid confusion, update the remaining documentation to reflect the Node 24 requirement (or reword to a supported range) so all setup instructions are consistent.

[mahata]

@copilot apply changes based on this feedback

[Copilot]

Updated the remaining docs reference in README to keep Node version requirements consistent at v24+. Addressed in commit 553bfa8.