* default to auto-caching only for npm package manager and documentation update
* refactor: enhance package manager detection for auto-caching
* add devEngines.packageManager detection logic for npm auto-caching
* chore: bump version to 6.0.0 and update documentation
* docs: update README and action.yml for npm caching logic clarification
* chore: update Node.js version in workflows
* chore: update Node.js versions in versions.yml
* chore: update rc Node.js version in versions.yml
* chore: switch macos-13 runner to macos-latest-large in workflow
* docs: update README and advanced usage documentation
* Change Node.js version to 24
Update Node.js version from 20 to 24 in action.yml
* update and vulnerability fixes
* update node version check
* update licences
* node version check update
* update version for test
* node version
* update node version to 24.0.0 in tool-versions and package-volta.json
* node 24
* update to 24
* update to specify engines
* check failures fix
* update package-lock.json
* licensed update
* check failure fix
* documentation update
---------
Co-authored-by: Aparna Jyothi <aparnajyothi-y@github.com>
The distinction between `secrets.GITHUB_TOKEN` and `secrets.NPM_TOKEN` cost myself and a colleague numerous hours when we were trying to fix a GitHub Actions workflow which needed to install a private package from a different repository from our GitHub organisation.
Given the issue dedicated to this point is closed, we should include a warning here to make it more clear why `secrets.GITHUB_TOKEN` will not work when passed to `npm ci`, in the presence of private packages from other GitHub Package repositories.
* Update documentation `actions/setup-node@v2` -> `actions/setup-node@v3`
* Bump workflows to `actions/setup-node@v3`
* Update `README.md` workflow status badges to new format
