Standardize actions/upload-artifact version across all CI workflows (v3 vs v4 inconsistency) #10689

Open
opened 2026-04-19 05:47:56 +00:00 by HAL9000 · 0 comments
Owner

Issue Description

The CI workflows use inconsistent versions of actions/upload-artifact:

  • ci.yml uses actions/upload-artifact@v3 (all jobs)
  • nightly-quality.yml uses actions/upload-artifact@v4 (quality reports upload)

This version mismatch creates maintenance risk and potential behavioral differences in artifact handling between workflows.

Impact

  • actions/upload-artifact@v3 and v4 have different behaviors (v4 changed artifact naming, retention, and download compatibility)
  • Artifacts uploaded with v3 cannot be downloaded with actions/download-artifact@v4 and vice versa
  • The release.yml uses actions/download-artifact@v3 to download the wheel artifact
  • Inconsistency makes it harder to reason about artifact compatibility across workflows

Expected Behavior

Standardize on @v4 (the current stable version) across all workflows.

Subtasks

  • Audit all workflow files for upload-artifact and download-artifact action versions
  • Standardize all to @v4 (or document a deliberate reason to stay on @v3)
  • Verify artifact upload/download compatibility after the change
  • Update release.yml's download-artifact step to match

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged.

Metadata

  • Commit Message: fix(ci): standardize actions/upload-artifact to v4 across all workflow files
  • Branch Name: fix/ci-artifact-action-version-consistency

Duplicate Check

Searched open and closed issues for: "artifact upload version", "upload-artifact v3 v4", "actions version inconsistency". No existing issues found.


Automated by CleverAgents Bot
Supervisor: Implementation Pool | Agent: implementation-worker

## Issue Description The CI workflows use inconsistent versions of `actions/upload-artifact`: - `ci.yml` uses `actions/upload-artifact@v3` (all jobs) - `nightly-quality.yml` uses `actions/upload-artifact@v4` (quality reports upload) This version mismatch creates maintenance risk and potential behavioral differences in artifact handling between workflows. ## Impact - `actions/upload-artifact@v3` and `v4` have different behaviors (v4 changed artifact naming, retention, and download compatibility) - Artifacts uploaded with v3 cannot be downloaded with `actions/download-artifact@v4` and vice versa - The `release.yml` uses `actions/download-artifact@v3` to download the wheel artifact - Inconsistency makes it harder to reason about artifact compatibility across workflows ## Expected Behavior Standardize on `@v4` (the current stable version) across all workflows. ## Subtasks - [ ] Audit all workflow files for `upload-artifact` and `download-artifact` action versions - [ ] Standardize all to `@v4` (or document a deliberate reason to stay on `@v3`) - [ ] Verify artifact upload/download compatibility after the change - [ ] Update `release.yml`'s `download-artifact` step to match ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged**. ## Metadata - **Commit Message**: `fix(ci): standardize actions/upload-artifact to v4 across all workflow files` - **Branch Name**: `fix/ci-artifact-action-version-consistency` ## Duplicate Check Searched open and closed issues for: "artifact upload version", "upload-artifact v3 v4", "actions version inconsistency". No existing issues found. --- **Automated by CleverAgents Bot** Supervisor: Implementation Pool | Agent: implementation-worker
HAL9000 added this to the v3.2.0 milestone 2026-04-19 05:47:56 +00:00
HAL9000 self-assigned this 2026-04-19 05:47:56 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#10689
No description provided.