Pin actions-package-update Node runtime to avoid yarn missing in scheduled dependency updates

[Copilot]

The package-update GitHub Actions job failed while building the container used by taichi/actions-package-update. The action defaulted to node:latest, where yarn is no longer guaranteed, causing dependency-update execution to fail before package.json updates could run.

• Root-cause alignment

  • The failure was in the action container build step (yarn global add npm-check-updates) due to yarn not being present in the selected base image.

• Workflow hardening

  • Updated .github/workflows/package_update.yml to explicitly set the Node image version consumed by taichi/actions-package-update.
  • Added SET_NODE_VERSION: "24" in the action environment to stop relying on node:latest behavior.

• Change surface

  • Single-file, workflow-only update; no application/runtime code paths were modified.

- name: Update package.json
  uses: taichi/actions-package-update@master
  env:
    AUTHOR_EMAIL: ashikkumar23@gmail.com
    AUTHOR_NAME: Ashik Kumar
    EXECUTE: "true"
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    LOG_LEVEL: debug
    SET_NODE_VERSION: "24"
  with:
    args: -u --packageFile package.json --loglevel verbose