Skip to content

Bump actions/upload-artifact from 4 to 7 #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
snapetech merged 1 commit into from
May 19, 2026
Merged

Bump actions/upload-artifact from 4 to 7 #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ jobs:
- name: Generate coverage report
run: cargo llvm-cov --workspace --lcov --output-path lcov.info || true
- name: Upload coverage report
uses: actions/upload-artifact@v4
uses: actions/upload-artifact@v7
Copy link
Copy Markdown

@kilo-code-bot kilo-code-bot Bot May 19, 2026

Choose a reason for hiding this comment

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

WARNING: Bumping actions/upload-artifact from v4 straight to v7 skips major versions v5 and v6, each of which introduced breaking requirements:

  • v5 bumped the minimum Actions Runner version to >= 2.315.0 (see upstream v5 release notes). If this repo uses any self-hosted runners below that version, this job will fail.
  • v6 further moved the default runs.using to node24, meaning node20 (the current default in GitHub hosted runners if not specified) is no longer sufficient.
  • v7 is ESM-only, which is transparent for plain uses: YAML workflows, but can surface if this workflow uses inline JavaScript expressions (e.g. ${{ }}). The action's runtime module is now type: module, so action consumers should be aware.

No code change in this file will cause a runtime error by itself, but these are environment/runner requirements that should be confirmed against the runner infrastructure before merging.

with:
name: coverage-report
path: lcov.info
Expand Down
Loading