Skip to content
This repository was archived by the owner on Aug 10, 2026. It is now read-only.
This repository was archived by the owner on Aug 10, 2026. It is now read-only.

CI: GitHub Actions Node.js 20 deprecation warning — update workflow to Node 24 #50

Description

@amar-python

Bug summary
GitHub Actions: Node.js 20 deprecation warning in workflows (actions forced to Node.js 24)

Bug description
GitHub Actions logs show a deprecation warning indicating the workflows target Node.js 20. The Actions runner is forcing those actions to run on Node.js 24, producing warnings in the run output. While this currently is a warning, unattended deprecation may cause future failures or unexpected behavior. Updating workflow job Node versions to a supported runtime will remove noise and ensure consistent CI environment.

Preconditions

  • Workflows located under .github/workflows/*.yml reference node-version: 20 (or implicitly target node 20 via an action that expects Node 20).
  • The repo uses actions/setup-node@v4 or similar actions that accept node-version.

Steps to reproduce

  1. Inspect workflow files under .github/workflows/. Look for node-version: 20 or other pinned values.
  2. Open any recent Actions run log (e.g., the job that produced the warning): https://github.com/amar-python/PostgreDataMigrationApp/actions/runs/31346507524/job/93329317109.
  3. Observe the warning: Node.js 20 is deprecated... are being forced to run on Node.js 24: actions/setup-node@v4.

Expected result

  • Workflows explicitly target a supported Node version (e.g., 24 or lts/*) and run without deprecation warnings.

Actual result

  • Workflows target Node 20 and CI logs contain deprecation warnings; runners currently map them to Node 24 but log a warning.

Suggested fix

  1. Edit workflow YAML files where Node is pinned and change node-version: 20 to node-version: 24 or node-version: 'lts/*'.
  2. If any action or dependency only supports Node 20, update the action or dependency to a Node-24-compatible version.
  3. Run a workflow re-run to confirm the warning is gone.

CI link
https://github.com/amar-python/PostgreDataMigrationApp/actions/runs/31346507524/job/93329317109

Notes

  • This change is low-risk but important for future-proofing the CI configuration. Recommend doing this before other CI churn to keep logs clean.

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions