[mikko-lab]

Updates only the JavaScript actions named in the Node 20 runtime warnings in .github/workflows/ci.yml:

Action	Release	Pinned commit
actions/checkout	v7.0.1	3d3c42e5aac5ba805825da76410c181273ba90b1
actions/setup-node	v7.0.0	820762786026740c76f36085b0efc47a31fe5020
pnpm/action-setup	v6.1.0	ea17c68df8912ef543352723c149a84f56e3d413
actions/upload-artifact	v7.0.1	043fb46d1a93c77aae656e7c1c64a875d1fc6a0a

All 25 references remain pinned to full commit SHAs with exact version comments. Release tag refs were resolved to commits (including peeling the annotated pnpm tag); each pinned upstream manifest declares runs.using: node24.

Application Node 22.23.2, pnpm 10.33.0, the blocking ubuntu-24.04-arm release gate, and the experimental amd64 diagnostic/non-blocking behavior are unchanged. After normalizing the four action pins/comments, the workflow is byte-for-byte identical to the base.

Validation:

• Full CI #7: all eight jobs succeeded on commit 007222b5ad43a34201337e35f0d34cf6d28cf077, including the arm64 release/golden-vector gate, WASM replay/integration, accessibility, Solidity/Anvil integration, and real browser E2E.
• All eight job logs inspected: no Node 20 JavaScript-action runtime warnings.
• Logs confirm application Node v22.23.2 and pnpm v10.33.0.
• Experimental amd64 validation itself still failed with the documented build-script SIGSEGV. The job remained non-blocking, emitted its expected warning, and the upgraded upload-artifact successfully uploaded amd64-crash-diagnostics (artifact ID 11466093119).
• Existing node --test scripts/ci-workflow.test.mjs and git diff --check pass.

No compatibility-regression fixes or other repository changes were necessary.