CI: bump upload-artifact (v4->v6) and download-artifact (v4->v7) to Node 24

Open Beginner friendly
#36,087 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
ci-cd

Research direction

Search the repository's GitHub Actions workflow files for upload-artifact@v4 and download-artifact@v4, then review each usage for the inputs and download patterns described in the issue. Update the action versions to v6 and v7, confirm no usage relies on artifact-ids, and verify the workflow changes pass CI.

Written by the indexing model from the issue text.

Description

stale Team : Maintenance Type : Task

Problem

Follow-up to #36085 (deferred there). actions/upload-artifact@v4 and actions/download-artifact@v4 run on Node 20 (deprecated; runners default to Node 24 on 2026-06-16). Their Node-24 releases are multi-major jumps, so they were split out for a reviewed bump.

Verified safe to bump

  • upload-artifact v4 → v6 — inputs identical (name, path, if-no-files-found, retention-days, compression-level, overwrite, include-hidden-files); only change is Node 24 + min Actions Runner 2.327.1 (our hosted ubuntu-24.04 runners satisfy this).
  • download-artifact v4 → v7 — inputs identical. The only behavioral break (v5) affects downloads by artifact-ids; every usage in this repo downloads by name or pattern/merge-multiple, never artifact-ids, so the migration guide's "no action needed" applies. (v7, not v8 — v8's no-unzip change is avoided.)

A FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 smoke-test already confirmed the existing v4 artifact actions run fine on Node 24, so this is not a cutover risk — it clears the deprecation warning.

Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 2h
Merged PRs (30d)
164

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotCMS/core

All issues in dotCMS/core

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.