Compare commits

...

5 Commits

Author SHA1 Message Date
Karl Horky
31bacb925a
Merge 9fe9d805a1 into 13427813f7 2025-10-08 08:27:38 -07:00
dependabot[bot]
13427813f7
Bump actions/publish-action from 0.3.0 to 0.4.0 (#1362)
Bumps [actions/publish-action](https://github.com/actions/publish-action) from 0.3.0 to 0.4.0.
- [Commits](https://github.com/actions/publish-action/compare/v0.3.0...v0.4.0)

---
updated-dependencies:
- dependency-name: actions/publish-action
  dependency-version: 0.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2025-10-08 09:32:50 -05:00
Karl Horky
9fe9d805a1
Clarify 2025-08-02 20:15:41 +02:00
Karl Horky
cadfbd215e
Make warning more apparent 2025-08-02 15:41:28 +02:00
Karl Horky
5db8d280d6
Add note about NVM and latest release syntax being outdated
Closes #1236 
Closes #1114
Closes #940

As extensively documented in #1236 and #940, the non-exact aliases `lts/*`, `*`, `current`, `latest`, and `22` are slow to be upgraded, lagging several days behind the Node.js releases.

Let users know about this downside.
2025-08-02 15:38:32 +02:00
2 changed files with 6 additions and 6 deletions

View File

@ -22,7 +22,7 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Update the ${{ env.TAG_NAME }} tag - name: Update the ${{ env.TAG_NAME }} tag
uses: actions/publish-action@v0.3.0 uses: actions/publish-action@v0.4.0
with: with:
source-tag: ${{ env.TAG_NAME }} source-tag: ${{ env.TAG_NAME }}
slack-webhook: ${{ secrets.SLACK_WEBHOOK }} slack-webhook: ${{ secrets.SLACK_WEBHOOK }}

View File

@ -132,12 +132,12 @@ The `node-version` input supports the Semantic Versioning Specification, for mor
Examples: Examples:
- Major versions: `18`, `20` - Specific versions: `10.15`, `16.15.1` , `18.4.0`
- More specific versions: `10.15`, `16.15.1` , `18.4.0` - Major versions (see Caveat below): `18`, `20`
- NVM LTS syntax: `lts/erbium`, `lts/fermium`, `lts/*`, `lts/-n` - NVM LTS syntax (see Caveat below): `lts/erbium`, `lts/fermium`, `lts/*`, `lts/-n`
- Latest release: `*` or `latest`/`current`/`node` - Latest release (see Caveat below): `*` or `latest`/`current`/`node`
**Note:** Like the other values, `*` will get the latest [locally-cached Node.js version](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md#nodejs), or the latest version from [actions/node-versions](https://github.com/actions/node-versions/blob/main/versions-manifest.json), depending on the [`check-latest`](docs/advanced-usage.md#check-latest-version) input. **Caveat:** If you require timely version upgrades, use specific versions like `22.18.0` and upgrade the versions yourself. Non-specific versions like `22`, `lts/*`, `*`, `latest`, etc. will get the latest [locally-cached Node.js version](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md#nodejs), or the latest version from [actions/node-versions](https://github.com/actions/node-versions/blob/main/versions-manifest.json), depending on the [`check-latest`](docs/advanced-usage.md#check-latest-version) input. Both of these sources can be slow to upgrade, with multiple days or weeks of lag time after the version release.
`current`/`latest`/`node` always resolve to the latest [dist version](https://nodejs.org/dist/index.json). `current`/`latest`/`node` always resolve to the latest [dist version](https://nodejs.org/dist/index.json).
That version is then downloaded from actions/node-versions if possible, or directly from Node.js if not. That version is then downloaded from actions/node-versions if possible, or directly from Node.js if not.