feat: improve node version resolution

[bilals12]

Node.js Version Resolution Enhancement

Problem

The action currently fails when using major version numbers (e.g., node: "20") in workflows, producing an error that lists all versions containing "20" without properly resolving to the latest stable version.

Solution

Enhanced the Node version resolution logic to:

1. Detect when a major version number is specified (e.g., "20")
2. Query the Node.js version registry to find all matching versions
3. Filter for stable versions matching the major version
4. Sort and select the latest compatible version
5. Install the resolved version

Changes

• Modified getNodeVersion() in node.js to handle major version numbers
• Added version resolution logic using Node.js version registry data
• Added comprehensive tests:
  • Unit tests for version resolution
  • Manual test script for local verification
  • GitHub Actions workflow for integration testing

Testing

• ✅ Unit tests pass (npm test)
• ✅ Manual testing with test script confirms:
  • Major version resolution (e.g., "20" -> "20.18.1")
  • Specific version handling (e.g., "20.18.1")
  • Error handling for invalid versions
• ✅ Added workflow tests for GitHub Actions environment

Example Usage

Major Version (Recommended)

- name: Setup Node.js
  uses: open-turo/action-setup-tools@v2
  with:
    node: "20"  # Will automatically use latest stable 20.x.x version

Specific Version

- name: Setup Node.js
  uses: open-turo/action-setup-tools@v2
  with:
    node: "20.18.1"  # Will use exact version

Using Version Files

The action also supports reading versions from standard Node.js version files:

Using .node-version

20.18.1

- name: Setup Node.js
  uses: open-turo/action-setup-tools@v2
  # Version will be read from .node-version file

Using .nvmrc

20

- name: Setup Node.js
  uses: open-turo/action-setup-tools@v2
  # Version will be read from .nvmrc file if .node-version is not present

The action will automatically:

1. Use any explicitly specified version in the workflow
2. Fall back to .node-version if present
3. Fall back to .nvmrc if present
4. Resolve major versions to latest stable releases

[github-actions]

Changes need to be built and committed to ./dist.

In your local repo, run:

npm run prepare
git commit -a --amend --no-edit
git push --force-with-lease

This will add those changes to your last commit, and get them pushed to the remote.

Changes need to be built and committed to ./dist.

In your local repo, run:

npm run prepare
git commit -a --amend --no-edit
git push --force-with-lease

This will add those changes to your last commit, and get them pushed to the remote.

Changes need to be built and committed to ./dist.

In your local repo, run:

npm run prepare
git commit -a --amend --no-edit
git push --force-with-lease

This will add those changes to your last commit, and get them pushed to the remote.

[github-actions]

Release notes preview

Below is a preview of the release notes if your PR gets merged.

---

2.1.0 (2025-01-21)

Bug Fixes

• adding updated dist files (110b53a)
• linting errors (f371eed)
• linting: addressing lint issues (6b5f1d1)
• package: resolving vulns via npm audit fix (7767eae)

Features

• add node version input parameter (837acb4)
• improve node version resolution (e423b97)
• support major version numbers in node version resolution (5b0fd51)