setup-node
setup-node copied to clipboard
actions
Set up your GitHub Actions workflow with a specific version of node.js
**Description:** Same github action triggered by tag creation worked 2 weeks ago, now it fails when trying to publish a new version to npm. **Action version:** using v4. **Platform:** -...
**Description:** When I supply a .npmrc file local, I run `npm publish` failed with `NEEDEDAUTH` error. But when I delete the local .npmrc, it will publish success in github action....
**Description:** Add warning and caveat for NVM syntax - to document [the surprising behavior that it will not use the latest `lts/*` version](https://github.com/actions/setup-node/issues/1236#issuecomment-2704241667) for days, weeks or months after a...
**Description:** A problem occurred while saving the yarn cache using a self-hosted runner. The process works correctly on the hosted runner. **Error :** ` Failed to save: Unable to reserve...
**Description:** For certain versions of node, `npm ci` hangs until github kills the workflow (about 6 hours). Failing versions: - 18 - 21 Working versions: - 16 - 18.5 `npm...
**Description:** After bumping the node-version used by an action, I find that I'm unable to merge a PR with the changes as the previous action is marked as required but...
Am getting the following error. EACCES: permission denied, mkdir '/home/gh-runner/actions-runner/_work/_tool/node/16.20.2' Falling back to download directly from Node Acquiring 16.20.2 - x64 from https://nodejs.org/dist/v16.20.2/node-v16.20.2-linux-x64.tar.gz Extracting ... /bin/tar xz --strip 1 --warning=no-unknown-keyword...
**Description:** Describe your changes. **Related issue:** Add link to the related issue. **Check list:** - [x] Mark if documentation changes are required. - [x] Mark if tests were added or...
**Description:** We needs to run a custom workflow to populate tools cache data for self-hosted runners. However it could not override the default downloading location on setup-node action. Setup-python already...
**Description:** In `docs/advanced-usage.md#node-version-file`, explain what effect `"engines": { "node": ">=16.0.0" }` would have had if it was not overridden by the volta option. **Justification:** I cannot tell from reading whether...
