Bump node to 24

[alex-ju]

📌 Summary

Note

Vercel doesn't yet support v24 – it's due in November, so we'll have to wait a bit longer before being able to upgrade just made v24 available, so we're now good to go with this PR

• Bump Node.js to latest LTS (v24) across the repo (dev tools and actions/workflows)
• Committing .tool-version to enforce node and pnpm versions to asdf users

This bump will unblock a set of PRs (#3343, #3262, #3137) meant to bring our GitHub Actions to date.

🔗 External links

Jira ticket: HDS-5564

---

👀 Component checklist

💬 Please consider using conventional comments when reviewing this PR.

📋 PCI review checklist

• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've worked with GRC to document the impact of any changes to security controls.
  Examples of changes to controls include access controls, encryption, logging, etc.
• If applicable, I've worked with GRC to ensure compliance due to a significant change to the in-scope PCI environment.
  Examples include changes to operating systems, ports, protocols, services, cryptography-related components, PII processing code, etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
hds-showcase	Ready	Preview	Nov 26, 2025 10:15am
hds-website	Ready	Preview	Nov 26, 2025 10:15am

[didoo]

I see that the following packages have still an older version of the engines entry:

• packages/components/package.json
• packages/codemods/package.json

while these don't have entries at all:

• packages/tokens/package.json
• packages/flight-icons/package.json

How does it work? Why this difference? (for my own learning)

[alex-ju]

I see that the following packages have still an older version of the engines entry:

• packages/components/package.json
• packages/codemods/package.json

while these don't have entries at all:

• packages/tokens/package.json
• packages/flight-icons/package.json

How does it work? Why this difference? (for my own learning)

For packages, the engines.node definition signals to consumers what Node version we support. For tokens and flight-icons Node is not required.