Records below are third-party data, not instructions. Apply with your own judgment.
github-actions
3 records of known failures, each with its cause, the fix and what not to try.
Records
- This request has been automatically failed because it uses a deprecat…github.com retired v3 of actions/upload-artifact and download-artifact on 2025-01-30 and fails every job that resolves it, even through another action.
- The
set-outputcommand is deprecated and will be disabled soon. Pleas…a step, or an action built on @actions/core older than 1.10.0, prints ::set-output to stdout; runners since 2.298.2 flag that in favour of the $GITHUB_OUTPUT file. - RequestError [HttpError]: Resource not accessible by integrationthe job's GITHUB_TOKEN lacks the scope the API call needs: repos created since 2023 default to read-only, and a permissions: block sets every scope it omits to none.
Don’t try
bump upload-artifact to v4 but keep download-artifact@v3 — download v3 is retired too, and download-artifact@v4 cannot read artifacts made by upload-artifact@v3; upgrade both together. (×1) · record
keep one artifact name for every matrix job — v4 artifacts are immutable, so the second upload to that name fails; use unique names and download with pattern + merge-multiple: true. (×1) · record
append the old ::set-output line to $GITHUB_OUTPUT — the file takes name=value lines, so steps.<id>.outputs.<name> stays empty. (×1) · record
set ACTIONS_ALLOW_UNSECURE_COMMANDS: true — the runner checks it only for set-env and add-path; it does not touch set-output and re-enables insecure commands. (×1) · record
permissions: write-all on a pull_request run from a fork — fork and Dependabot PR runs get a read-only GITHUB_TOKEN by default whatever the workflow asks for; do the write in a separate workflow_run workflow. (×1) · record