Bump pipeline action versions

[JonasDov]

• Bumped node to 24.15.0.
• actions/checkout to 6.0.2
• actions/setup-node to 6.4.0
• pnpm/action-setup to 6.0.8
• Pinned github actions in workflows to specific commit instead of version.

[Copilot]

Pull request overview

This PR updates CI/workflow dependencies by upgrading the Node.js runtime used in GitHub Actions and pinning key workflow actions to specific commit SHAs for supply-chain hardening.

Changes:

• Updated workflows to use Node.js 24.15.0 (from 22).
• Pinned actions/checkout, actions/setup-node, and pnpm/action-setup to specific commit SHAs instead of version tags.
• Updated workflows to use the new pinned action references consistently across CI/E2E/benchmark jobs.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
.github/workflows/sanity.yml	Pins actions/checkout to a commit SHA in the sanity workflow.
.github/workflows/extract-api.yml	Pins checkout/pnpm/setup-node and bumps Node to 24.15.0 for API extraction.
.github/workflows/e2e.yml	Pins checkout/pnpm/setup-node and bumps Node to 24.15.0 across E2E jobs.
.github/workflows/codeql.yml	Pins actions/checkout to a commit SHA in the CodeQL workflow.
.github/workflows/ci.yml	Pins checkout/pnpm/setup-node and bumps Node to 24.15.0 across CI jobs.
.github/workflows/changeset-release.yml	Bumps release workflow Node version to 24.15.0.
.github/workflows/benchmark-tree-widget.yml	Pins checkout/pnpm/setup-node and bumps Node to 24.15.0 for benchmarks.
.github/workflows/benchmark-pr-tree-widget.yml	Pins checkout/pnpm/setup-node and bumps Node to 24.15.0 for PR benchmarks.

Suppressed comments (6)

.github/workflows/e2e.yml:79

• The pnpm setup step no longer pins a pnpm version. That makes CI runs dependent on whatever pnpm version the action installs by default, which can drift over time. Since the repo already declares packageManager: pnpm@11.20.0 in package.json, consider explicitly pinning the action's version input to match for reproducible installs.

      - name: Install pnpm
        uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093

.github/workflows/e2e.yml:123

• The pnpm setup step no longer pins a pnpm version. That makes CI runs dependent on whatever pnpm version the action installs by default, which can drift over time. Since the repo already declares packageManager: pnpm@11.20.0 in package.json, consider explicitly pinning the action's version input to match for reproducible installs.

      - name: Install pnpm
        uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093

.github/workflows/ci.yml:37

• pnpm/action-setup is pinned to a commit but the pnpm version isn't pinned. If the action default changes, CI may start using a different pnpm version unexpectedly. Since the repo declares packageManager: pnpm@11.20.0 in package.json, consider setting with: version: 11.20.0 here for reproducibility.

      - name: Setup pnpm
        uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093

.github/workflows/ci.yml:59

• pnpm/action-setup is pinned to a commit but the pnpm version isn't pinned. If the action default changes, CI may start using a different pnpm version unexpectedly. Since the repo declares packageManager: pnpm@11.20.0 in package.json, consider setting with: version: 11.20.0 here for reproducibility.

      - name: Setup pnpm
        uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093

.github/workflows/ci.yml:80

• pnpm/action-setup is pinned to a commit but the pnpm version isn't pinned. If the action default changes, CI may start using a different pnpm version unexpectedly. Since the repo declares packageManager: pnpm@11.20.0 in package.json, consider setting with: version: 11.20.0 here for reproducibility.

      - name: Setup pnpm
        uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093

.github/workflows/ci.yml:110

• pnpm/action-setup is pinned to a commit but the pnpm version isn't pinned. If the action default changes, CI may start using a different pnpm version unexpectedly. Since the repo declares packageManager: pnpm@11.20.0 in package.json, consider setting with: version: 11.20.0 here for reproducibility.

      - name: Setup pnpm
        uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

Tree-Widget benchmark

Benchmark suite	Current: ec68700	Previous: 8df07d4	Deviation	Status
models tree creates initial filtered view for 50k target items	752 ms	1071 ms	-29.79%	✅
models tree creates initial filtered view for 50k target items (P95 of main thread blocks)	92 ms	95 ms	-3.16%	〰️
models tree validates categories visibility for imodel with 50k categories	6107 ms	12371 ms	-50.63%	✅
models tree validates categories visibility for imodel with 50k categories (P95 of main thread blocks)	72 ms	85 ms	-15.29%	〰️
models tree changing model visibility changes visibility for 50k elements	2313 ms	3371 ms	-31.39%	✅
models tree changing model visibility changes visibility for 50k elements (P95 of main thread blocks)	0 ms	123 ms	-100%	✅
models tree changing category visibility changes visibility for 50k elements	2343 ms	3344 ms	-29.93%	✅
models tree changing category visibility changes visibility for 50k elements (P95 of main thread blocks)	0 ms	23 ms	-100%	〰️
models tree changing per-model-category override changes visibility for 50k elements	2330 ms	3301 ms	-29.42%	✅
models tree changing per-model-category override changes visibility for 50k elements (P95 of main thread blocks)	0 ms	0 ms	0%	🟰
models tree changing element visibility changes only parent nodes visibility with 50k elements	3872 ms	4669 ms	-17.07%	✅
models tree changing element visibility changes only parent nodes visibility with 50k elements (P95 of main thread blocks)	90 ms	89 ms	1.12%	〰️
categories tree creates initial filtered view for 50k items	1606 ms	1515 ms	6.01%	〰️
categories tree creates initial filtered view for 50k items (P95 of main thread blocks)	605 ms	303 ms	99.67%	🚨
categories tree changing definition container visibility changes visibility for 50k subCategories	2401 ms	2811 ms	-14.59%	✅
categories tree changing definition container visibility changes visibility for 50k subCategories (P95 of main thread blocks)	38 ms	57 ms	-33.33%	〰️
categories tree changing definition container visibility changes visibility for 50k categories	4889 ms	5886 ms	-16.94%	✅
categories tree changing definition container visibility changes visibility for 50k categories (P95 of main thread blocks)	101 ms	126 ms	-19.84%	〰️

This comment was automatically generated by workflow using github-action-benchmark.