Update GitHub Action to setup-node@v6

[MamunC0der]

Replaced uses: actions/setup-node@v5 → uses: actions/setup-node@v6

Reason:
Version v6 improves compatibility with Node.js 22+, enhances cache performance, and supports the latest GitHub Actions runtime optimizations.
Release notes: https://github.com/actions/setup-node/releases/tag/v6.0.0

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	7c6a59c
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/68efb5b224b0640008d5ffaf
😎 Deploy Preview	https://deploy-preview-16496--ethereumorg.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 44 (🔴 down 16 from production) Accessibility: 94 (no change from production) Best Practices: 92 (🔴 down 8 from production) SEO: 92 (no change from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[wackerow]

@claude please review

[claude]

Claude finished @wackerow's task —— View job

---

PR Review: Update GitHub Action to setup-node@v6

I've completed my analysis of the workflow file changes. Here's my comprehensive review:

✅ What's Good

Consistent Pattern: All 9 workflow files follow the same upgrade pattern from actions/setup-node@v5 to actions/setup-node@v6, which shows thorough attention to detail.

Good Rationale: The upgrade to v6 is well-justified - it provides better Node.js 22+ compatibility, improved cache performance, and latest GitHub Actions runtime optimizations.

🔍 Issues Found

1. Inconsistency in chromatic.yml

• File: .github/workflows/chromatic.yml:35
• Issue: Still shows actions/setup-node@v5 in the file I read, but should be updated to v6
• Impact: May not get the v6 benefits for Chromatic builds

2. Node Version Consistency in playwright.yml

• File: .github/workflows/playwright.yml
• Lines: 12 and 56
• Issue: Two different setup-node steps with different node versions:
  • Line 12: node-version: lts/*
  • Line 56: node-version: 22.12.0
• Recommendation: Consider standardizing on a specific Node.js version or document why different versions are needed for different jobs

3. Missing Cache Configuration

• Files: Several workflows
• Issue: Some setup-node steps don't specify cache: 'pnpm' parameter
• Example: playwright.yml:12 lacks cache configuration while playwright.yml:56 includes it
• Impact: Missing build performance improvements from pnpm cache

📋 Verification Checklist

• Analyze all 9 changed workflow files
• Check consistency of setup-node@v6 usage across files
• Review Node.js version compatibility
• Look for any missing configurations or potential issues
• Provide comprehensive review feedback

🎯 Recommendations

1. Verify chromatic.yml Update: Double-check that chromatic.yml:35 was properly updated to @v6
2. Standardize Cache Configuration: Add cache: 'pnpm' to setup-node steps that are missing it
3. Document Node Version Strategy: Consider documenting why different Node.js versions are used across workflows
4. Test Workflows: Ensure all automated workflows still function correctly with setup-node@v6

🔒 Security & Performance

No security concerns identified. The upgrade should improve performance through better caching and Node.js 22+ compatibility.

✅ Overall Assessment

This is a good maintenance PR that keeps the project's CI/CD infrastructure up-to-date. The identified issues are minor and don't block the upgrade. The changes align well with maintaining modern tooling standards.

Recommendation: ✅ Approve with minor fixes for the cache configuration inconsistencies.

[wackerow]

Looks good, thanks @MamunC0der

[wackerow]

@all-contributors please add @MamunC0der for maintenance

[allcontributors]

@wackerow

@MamunC0der already contributed before to maintenance