chore(deps): bump actions/upload-artifact from 4 to 7#7856
Conversation
dependabot
Bot
added
dependencies
github_actions
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4 to 7. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v4...v7) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions/upload-artifact-7
branch
from
e7f4fb3 to
b1c1454
Compare
LifeOps Multi-Tier BenchmarkSuite:
|
LifeOpsBench (Python) — smokeRun ID:
Full artifacts: |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| --bundle "${{ github.event.inputs.bundle || 'eliza-1-9b' }}" \ | ||
| | tee gpu-plan.json | ||
| - name: upload plan | ||
| uses: actions/upload-artifact@v4 | ||
| uses: actions/upload-artifact@v7 | ||
| with: | ||
| name: gpu-plan | ||
| path: gpu-plan.json |
There was a problem hiding this comment.
Starting with v6, actions/upload-artifact requires Actions Runner ≥ 2.327.1 (Node.js 24 runtime). Both upload steps in this workflow run on [self-hosted, linux, gpu, cuda]. If that pool is below 2.327.1, these steps will fail at runtime. GitHub-hosted runners satisfy the requirement automatically; self-hosted GPU pools need manual verification and upgrade before this bump is safe.
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
LifeOps Multi-Tier BenchmarkSuite:
|
LifeOps Multi-Tier BenchmarkSuite:
|
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
LifeOps Benchmark —
|
LifeOps Benchmark —
|
LifeOps Multi-Tier BenchmarkSuite:
|
LifeOpsBench (Python) — smokeRun ID:
Full artifacts: |
2 participants
Bumps actions/upload-artifact from 4 to 7.
Release notes
Sourced from actions/upload-artifact's releases.
... (truncated)
Commits
043fb46Merge pull request #797 from actions/yacaovsnc/update-dependency634250cInclude changes in typespec/ts-http-runtime 0.3.5e454baaReadme: bump all the example versions to v7 (#796)74fad66Update the readme with direct upload details (#795)bbbca2dSupport direct file uploads (#764)589182cUpgrade the module to ESM and bump dependencies (#762)47309c9Merge pull request #754 from actions/Link-/add-proxy-integration-tests02a8460Add proxy integration testb7c566aMerge pull request #745 from actions/upload-artifact-v6-releasee516bc8docs: correct description of Node.js 24 support in READMEGreptile Summary
This PR bumps
actions/upload-artifactfrom v4 to v7 across 47 GitHub Actions workflow files. The change is entirely mechanical — every modification is a single-line version tag replacement with no logic or configuration changes.archive: falsedirect-upload option. None of the workflows use any new parameters, so the API surface is unchanged.ubuntu-*,macos-*,windows-*) are satisfied automatically. Several workflows runupload-artifacton self-hosted runner pools; v6 introduced a hard minimum of Actions Runner 2.327.1 that v7 also requires — those pools must be verified before this is safe to merge.Confidence Score: 4/5
Safe to merge for all GitHub-hosted runner workflows; self-hosted GPU/KVM/macOS pools must be verified as running Actions Runner ≥ 2.327.1 before the affected workflows will continue to work.
The change is mechanical across 47 files — every edit is a single-line version tag replacement. Workflows running on GitHub-hosted runners carry no risk. The concern is the seven workflows that invoke upload-artifact on self-hosted pools: v6 introduced a hard Node.js 24 runtime requirement, and v7 carries the same constraint. If those pools are below the minimum runner version, the artifact upload steps will fail at runtime with no fallback.
training-stack.yml, gpu-bench-nightly.yml, elizaos-openagent-ai-soc.yml, build-llama-ffi-linux.yml, build-omnivoice.yml, local-inference-matrix.yml, scenario-matrix.yml — all use self-hosted runner pools where the Node.js 24 runtime requirement must be manually confirmed.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[actions/upload-artifact bump v4 → v7] --> B{Runner type?} B -->|GitHub-hosted\nubuntu-*/macos-*/windows-*| C[✅ Safe\nNode 24 satisfied automatically] B -->|Self-hosted| D{Runner version\n≥ 2.327.1?} D -->|Yes| E[✅ Safe] D -->|No / Unknown| F[❌ upload-artifact steps\nfail at runtime] F --> G[Affected workflows:\ngpu-bench-nightly\ntraining-stack\nelizaos-openagent-ai-soc\nbuild-llama-ffi-linux\nbuild-omnivoice\nlocal-inference-matrix\nscenario-matrix]Comments Outside Diff (1)
.github/workflows/training-stack.yml, line 836-840 (link)v6introduced a hard minimum Actions Runner version of 2.327.1 (Node.js 24 runtime), andv7carries the same requirement. This workflow runsupload-artifacton[self-hosted, gpu-cuda-12.6]; if that pool is below 2.327.1 the artifact upload steps will fail at runtime. The same constraint applies to at least four other changed workflows in this PR that also use self-hosted pools:build-llama-ffi-linux.yml([self-hosted, gpu, cuda]),build-omnivoice.yml([self-hosted, gpu, cuda]),local-inference-matrix.yml([self-hosted, gpu, cuda]), andscenario-matrix.yml([self-hosted, eliza-e2e-macos]). GitHub-hosted runners onubuntu-latestsatisfy this automatically; self-hosted pools must be manually verified and updated before this change is safe to merge.Reviews (6): Last reviewed commit: "Merge branch 'develop' into dependabot/g..." | Re-trigger Greptile