Migrate actions/upload-artifact to a Node.js 24-compatible release

[MariusStorhaug]

actions/upload-artifact is used by the Build-Site workflow in PR #45 to publish workflow artifacts. During review, workflow logs reported a deprecation warning indicating that Node.js 20-based actions are being sunset and that this dependency will be forced to Node.js 24 starting June 2nd, 2026, with Node.js 20 removed on September 16th, 2026.

Request

User impact

The current workflow behavior risks future CI instability once the deprecation timeline is enforced. If the pinned actions/upload-artifact revision does not support the new runtime, artifact upload steps in Build-Site may fail or behave unexpectedly, reducing confidence in release and documentation automation.

What is expected

The Build-Site workflow should use a release or commit pin of actions/upload-artifact that is explicitly compatible with Node.js 24, and workflow execution should continue to produce and upload artifacts without regressions.

Evidence

• Workflow context: Build-Site job logs observed while reviewing PR #45
• Reported warning: Node.js 20 actions are deprecated... actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 ... forced to Node.js 24 starting June 2nd, 2026; Node.js 20 removed September 16th, 2026.

Acceptance criteria

• Build-Site updates actions/upload-artifact to a Node.js 24-compatible release or commit pin
• The chosen version/pin is documented in workflow comments or issue notes for traceability
• At least one workflow run verifies artifact upload success after migration
• No new warnings or failures are introduced in artifact upload steps

---

Technical decisions

Scope of change: Limit updates to workflow definitions that reference actions/upload-artifact, starting with Build-Site and then any additional matches discovered in the repository.

Versioning strategy: Prefer pinning to a specific commit SHA from a release that is documented as Node.js 24-compatible in the actions/upload-artifact repository and related GitHub Actions documentation.

Migration guidance: Replace the deprecated pin (ea165f8d65b6e75b540449e92b4886f43607fa02) with a Node.js 24-compatible pin, keep explicit pinning for supply-chain safety, and avoid floating major-only tags without a corresponding trusted digest.

Verification strategy: Validate workflow behavior by running the updated Build-Site workflow and confirming artifact upload/download lifecycle is intact (artifact appears in run summary and is retrievable).

Compatibility risk management: If additional workflow jobs use the same deprecated revision, migrate all occurrences in the same change to avoid staggered failures.

---

Implementation plan

Discovery

• Search all workflow files for actions/upload-artifact references and identify deprecated pins
• Confirm the currently pinned revision(s) and capture affected workflow/job names

Migration

• Select a Node.js 24-compatible actions/upload-artifact release and commit SHA
• Update Build-Site workflow to the selected pin
• Update any additional affected workflow references to the same vetted pin

Verification

• Execute or rerun the Build-Site workflow after the update
• Confirm artifact upload completes successfully and artifacts are downloadable
• Confirm deprecation warning related to Node.js 20 for actions/upload-artifact is no longer present

Documentation

• Add a concise note in workflow comments or related docs indicating why this pin was chosen and when it was updated
• Link the validation run in the issue before closing

[MariusStorhaug]

Closing: this deprecation originates from the Process-PSModule reusable workflow framework, not from the Sodium module itself. Please track in the PSModule framework repository.