diff --git a/README.md b/README.md index 92804e94..7a4e0056 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ See [action.yml](action.yml) ```yaml -- uses: actions/setup-node@v4 +- uses: actions/setup-node@v5 with: # Version Spec of the version to use in SemVer notation. # It also admits such aliases as lts/*, latest, nightly and canary builds @@ -98,8 +98,8 @@ See [action.yml](action.yml) ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: 18 - run: npm ci @@ -147,8 +147,8 @@ See the examples of using cache for `yarn`/`pnpm` and `cache-dependency-path` in ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: 20 cache: 'npm' @@ -160,8 +160,8 @@ steps: ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: 20 cache: 'npm' @@ -181,9 +181,9 @@ jobs: node: [ 14, 16, 18 ] name: Node ${{ matrix.node }} sample steps: - - uses: actions/checkout@v4 + - uses: actions/checkout@v5 - name: Setup node - uses: actions/setup-node@v4 + uses: actions/setup-node@v5 with: node-version: ${{ matrix.node }} - run: npm ci @@ -197,7 +197,7 @@ jobs: To get a higher rate limit, you can [generate a personal access token on github.com](https://github.com/settings/tokens/new) and pass it as the `token` input for the action: ```yaml -uses: actions/setup-node@v4 +uses: actions/setup-node@v5 with: token: ${{ secrets.GH_DOTCOM_TOKEN }} node-version: 20 diff --git a/docs/advanced-usage.md b/docs/advanced-usage.md index 856c5efa..97f977f7 100644 --- a/docs/advanced-usage.md +++ b/docs/advanced-usage.md @@ -45,8 +45,8 @@ If `check-latest` is set to `true`, the action first checks if the cached versio ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: '16' check-latest: true @@ -63,8 +63,8 @@ See [supported version syntax](https://github.com/actions/setup-node#supported-v ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version-file: '.nvmrc' - run: npm ci @@ -97,8 +97,8 @@ jobs: runs-on: windows-latest name: Node sample steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 + - uses: actions/checkout@v5 + - uses: actions/setup-node@v5 with: node-version: '14' architecture: 'x64' # optional, x64 or x86. If not specified, x64 will be used by default @@ -118,8 +118,8 @@ jobs: runs-on: ubuntu-latest name: Node sample steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 + - uses: actions/checkout@v5 + - uses: actions/setup-node@v5 with: node-version: '20.0.0-v8-canary' # it will install the latest v8 canary release for node 20.0.0 - run: npm ci @@ -133,8 +133,8 @@ jobs: runs-on: ubuntu-latest name: Node sample steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 + - uses: actions/checkout@v5 + - uses: actions/setup-node@v5 with: node-version: '20-v8-canary' # it will install the latest v8 canary release for node 20 - run: npm ci @@ -149,8 +149,8 @@ jobs: runs-on: ubuntu-latest name: Node sample steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 + - uses: actions/checkout@v5 + - uses: actions/setup-node@v5 with: node-version: 'v20.1.1-v8-canary20221103f7e2421e91' - run: npm ci @@ -169,8 +169,8 @@ jobs: runs-on: ubuntu-latest name: Node sample steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 + - uses: actions/checkout@v5 + - uses: actions/setup-node@v5 with: node-version: '16-nightly' # it will install the latest nightly release for node 16 - run: npm ci @@ -185,8 +185,8 @@ jobs: runs-on: ubuntu-latest name: Node sample steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 + - uses: actions/checkout@v5 + - uses: actions/setup-node@v5 with: node-version: '16.0.0-nightly' # it will install the latest nightly release for node 16.0.0 - run: npm ci @@ -201,8 +201,8 @@ jobs: runs-on: ubuntu-latest name: Node sample steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 + - uses: actions/checkout@v5 + - uses: actions/setup-node@v5 with: node-version: '16.0.0-nightly20210420a0261d231c' - run: npm ci @@ -219,8 +219,8 @@ jobs: runs-on: ubuntu-latest name: Node sample steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 + - uses: actions/checkout@v5 + - uses: actions/setup-node@v5 with: node-version: '16.0.0-rc.1' - run: npm ci @@ -236,8 +236,8 @@ The action follows [actions/cache](https://github.com/actions/cache/blob/main/ex Yarn caching handles both yarn versions: 1 or 2. ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: '14' cache: 'yarn' @@ -255,11 +255,11 @@ steps: # NOTE: pnpm caching support requires pnpm version >= 6.10.0 steps: -- uses: actions/checkout@v4 +- uses: actions/checkout@v5 - uses: pnpm/action-setup@v2 with: version: 6.32.9 -- uses: actions/setup-node@v4 +- uses: actions/setup-node@v5 with: node-version: '14' cache: 'pnpm' @@ -274,8 +274,8 @@ steps: **Using wildcard patterns to cache dependencies** ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: '14' cache: 'npm' @@ -287,8 +287,8 @@ steps: **Using a list of file paths to cache dependencies** ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: '14' cache: 'npm' @@ -324,9 +324,9 @@ jobs: architecture: x86 name: Node ${{ matrix.node_version }} - ${{ matrix.architecture }} on ${{ matrix.os }} steps: - - uses: actions/checkout@v4 + - uses: actions/checkout@v5 - name: Setup node - uses: actions/setup-node@v4 + uses: actions/setup-node@v5 with: node-version: ${{ matrix.node_version }} architecture: ${{ matrix.architecture }} @@ -337,8 +337,8 @@ jobs: ## Publish to npmjs and GPR with npm ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: '14.x' registry-url: 'https://registry.npmjs.org' @@ -346,7 +346,7 @@ steps: - run: npm publish env: NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} -- uses: actions/setup-node@v4 +- uses: actions/setup-node@v5 with: registry-url: 'https://npm.pkg.github.com' - run: npm publish @@ -357,8 +357,8 @@ steps: ## Publish to npmjs and GPR with yarn ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: '14.x' registry-url: @@ -366,7 +366,7 @@ steps: - run: yarn publish env: NODE_AUTH_TOKEN: ${{ secrets.YARN_TOKEN }} -- uses: actions/setup-node@v4 +- uses: actions/setup-node@v5 with: registry-url: 'https://npm.pkg.github.com' - run: yarn publish @@ -377,8 +377,8 @@ steps: ## Use private packages ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: '14.x' registry-url: 'https://registry.npmjs.org' @@ -397,8 +397,8 @@ Below you can find a sample "Setup .yarnrc.yml" step, that is going to allow you ```yaml steps: -- uses: actions/checkout@v4 -- uses: actions/setup-node@v4 +- uses: actions/checkout@v5 +- uses: actions/setup-node@v5 with: node-version: '14.x' - name: Setup .yarnrc.yml @@ -427,7 +427,7 @@ It is possible to specify a token to authenticate with the mirror using the `mir The token will be passed as a bearer token in the `Authorization` header. ```yaml -- uses: actions/setup-node@v4 +- uses: actions/setup-node@v5 with: node-version: '14.x' mirror: 'https://nodejs.org/dist'