Tool versions for asdf version manager

[daniel-richter]

Set Node.js version for asdf version manager

• Add .tool-versions file for Node.js version management
  • GitHub Actions are bound to Node 20.x
• Disable major updates for asdf manager in Renovate configuration

---

This change consolidates Node.js version management by migrating from individual .node-version files to a centralized .tool-versions file using the asdf tool format. The GitHub Actions workflow is updated to reference the new unified version file, and Renovate configuration is modified to disable major version updates for asdf-managed dependencies.

Walkthrough

• Chore: Standardized Node.js version management across the project by replacing multiple .node-version files with a single .tool-versions file
• Chore: Updated CI/CD pipeline to use the centralized version configuration for both PR Summary and PR Review build processes
• Chore: Enhanced dependency management by configuring Renovate to handle asdf tool versions while preventing disruptive major version updates

_{Model: anthropic--claude-4-sonnet | Prompt Tokens: 664 | Completion Tokens: 173}

[github-actions]

This change pins the project’s Node.js runtime to v22.17.1 and adjusts the Renovate configuration to include an asdf manager, specifically disabling its major version updates to prevent disruptive jumps.

Walkthrough

• Chore: Pinned Node.js to v22.17.1 in .tool-versions for consistent local and CI environments.
• Chore: Added asdf as a Renovate matchManager but disabled its major updates to avoid unexpected breaking changes.

_{Model: o4-mini | Prompt Tokens: 298 | Completion Tokens: 440}

[github-actions]

Here is a friendly overview of your code enhanced by AI. These suggestions are best-effort ideas, so treat them as possible options rather than certainties. You know your goals and context best, so feel free to pick and choose what fits. Trust your judgment—AI is here to support not replace your expertise.
_{Model: o4-mini | Prompt Tokens: 740 | Completion Tokens: 3276}

[github-actions]

Updated the CI workflow to centralize Node version management using the root .tool-versions file, removing the outdated per-package .node-version files for PR Summary and PR Review steps.

Walkthrough

• Chore: Consolidate Node version configuration under a single .tool-versions file
• Chore: Remove legacy .node-version files from PR Summary and PR Review
• Chore: Maintain npm caching with updated dependency paths

_{Model: o4-mini | Prompt Tokens: 462 | Completion Tokens: 752 | Diff Range: 516d4e0...3ca9db9}

[github-actions]

Below is a friendly overview of your code with AI assistance. These ideas are suggestions, not absolute truths, so use what fits best. You’re in charge of decisions and creative direction—AI is simply here to offer support.
_{Model: o4-mini | Prompt Tokens: 916 | Completion Tokens: 5162 | Diff Range: 516d4e0...3ca9db9}

[github-actions]

This update adjusts the Node.js runtime version in the project configuration from 22.17.1 to the more stable LTS release 20.19.4, ensuring consistent environments across development and CI.

Walkthrough

• Chore: Downgraded Node.js to v20.19.4 LTS to improve compatibility and stability for all contributors.

_{Model: o4-mini | Prompt Tokens: 223 | Completion Tokens: 413 | Diff Range: 3ca9db9...6f7326a}

[github-actions]

Here's a collaborative code review enhanced by AI assistance. These suggestions offer helpful insights and patterns, though they're recommendations rather than absolute requirements. You maintain full control over implementation choices—AI simply provides additional perspective to support your decision-making process. Use whatever feels most valuable for your project.
_{Model: anthropic--claude-4-sonnet | Prompt Tokens: 1228 | Completion Tokens: 543}

[github-actions]

There's an inconsistency in the step names. The first setup is for "PR Summary" but the second build step is also labeled "PR Summary" instead of "PR Review". This creates confusion and makes debugging harder.

- name: Build (PR Review)

This should match the context of the PR Review setup step above it.

[github-actions]

Consider adding a comment to explain the purpose of this file and the Node.js version choice. This improves maintainability and helps other developers understand the tooling decisions.

# asdf tool versions file
# Node.js version used across the project
nodejs 20.19.4

Also, ensure this Node.js version (20.19.4) is the intended version, as it appears you're downgrading from 22.17.1 based on the deleted files.