Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ You are welcome to still raise bugs in this repo.

## GHES Support

`upload-artifact@v4+` is not currently supported on GitHub Enterprise Server (GHES). If you are on GHES, you must use [v3.2.2](https://github.com/actions/upload-artifact/releases/tag/v3.2.2) (Node 24) or [v3.2.2-node20](https://github.com/actions/upload-artifact/releases/tag/v3.2.2-node20) (Node 20).
`upload-artifact@v4+` is not currently supported on GitHub Enterprise Server (GHES). If you are on GHES, you must use [v3.2.2](https://github.com/actions/upload-artifact/releases/tag/v3.2.2) (latest Node LTS) or [v3.2.2-node20](https://github.com/actions/upload-artifact/releases/tag/v3.2.2-node20) (Node 20).
Copy link

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR title says the generic v3 tag will track the latest Node LTS, but this sentence links to a pinned patch tag (v3.2.2) and labels it “latest Node LTS”. A fixed patch release won’t update when Node’s LTS changes, so this wording is likely to become misleading. Consider either (a) referencing the major tag (e.g., actions/upload-artifact@v3) when describing the moving “latest LTS” target, or (b) keeping an explicit Node version for v3.2.2 (and optionally add a separate note that the v3 major tag tracks the latest LTS).

Copilot uses AI. Check for mistakes.

## Usage

Expand Down
Loading