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

[MariusStorhaug]

The CI workflow for GoogleFonts emitted a platform deprecation warning during review of PR #210 on branch perf/install-improvements, and the warning indicates upcoming runtime enforcement dates that can cause workflow failures if unaddressed.

Request

User impact

Repository maintainers need CI runs to remain stable and warning-free as GitHub-hosted action runtimes transition from Node.js 20 to Node.js 24 defaults, otherwise routine validation and release confidence can be disrupted near enforcement dates.

Current experience

Workflow logs report that Node.js 20-based actions are deprecated and will be forced to Node.js 24 by default starting June 2, 2026, with removal on Sept 16, 2026. The specific pinned action in use is actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, observed at Process-PSModule / Build-Site / Build-Site.

Desired experience

Workflows use a Node.js 24-compatible release of actions/upload-artifact, and the relevant jobs complete without runtime deprecation warnings or regressions in artifact upload behavior.

Acceptance criteria

• Replace the current actions/upload-artifact pin with a Node.js 24-compatible release in affected workflow(s)
• Verify Process-PSModule / Build-Site / Build-Site completes successfully after the update
• Confirm artifact upload outputs and retention behavior remain correct
• Confirm deprecation warning is no longer present in new workflow run logs
• Document the action version update in the change history or PR notes

---

Technical decisions

Scope: Start with the workflow location identified in logs (Process-PSModule / Build-Site / Build-Site) and expand only if other workflow files reference the same deprecated pin.

Versioning approach: Keep actions pinned to an immutable reference (commit SHA) while moving to a release that is explicitly compatible with Node.js 24, preserving supply-chain integrity and deterministic builds.

Validation strategy: Validate in CI by triggering the affected workflow path and checking both job success and warning-free logs for the updated steps.

Backward compatibility: No user-facing module API behavior is expected to change; this is maintenance work limited to CI workflow configuration.

---

Implementation plan

Discovery

• Locate all actions/upload-artifact usages in repository workflows
• Identify the currently pinned references and confirm which are affected by the deprecation warning

Workflow updates

• Update affected workflow file(s) to a Node.js 24-compatible actions/upload-artifact reference
• Keep pinning strategy consistent with existing repository security posture

Validation

• Run CI on branch with workflow changes and inspect Process-PSModule / Build-Site / Build-Site
• Verify artifacts are uploaded and accessible as expected
• Verify logs no longer contain the Node.js 20 deprecation warning

Follow-up

• Link validation run(s) in issue comments for traceability
• Close issue once compatibility and behavior are confirmed