Skip to content

CI on Node 24 actions; Node.js 26 for CI and the frontend image - #7

Merged
k3mpaxl merged 2 commits into
mainfrom
ci/node24-actions
Oct 7, 2026
Merged

k3mpaxl merged 2 commits into
mainfrom
ci/node24-actions

Conversation

@k3mpaxl

@k3mpaxl k3mpaxl commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Why

Every job showed the annotation "Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24 …". That covered checkout, setup-python, setup-node and all docker/* actions in CI and in the Docker publish workflow.

What changed

  • Actions on their current major versions, which all run on Node 24:

    Action Before After
    actions/checkout v4 v7
    actions/setup-python v5 v7
    actions/setup-node v4 v7
    actions/upload-artifact v4 v7
    docker/setup-buildx-action v3 v4
    docker/setup-qemu-action v3 v4
    docker/login-action v3 v4
    docker/build-push-action v6 v7
    docker/metadata-action v5 v6
  • Node.js 26 for CI (node-version: '26') and for the frontend stage of the Docker image (node:26-alpine, available for amd64 and arm64), instead of 22. 26.10.0 is the current release; the 26 line becomes LTS at the end of October 2026.

  • README: the documented minimum stays Node.js 20+ (Vite and Playwright accept 20+); it now notes that the image and CI use Python 3.14 and Node.js 26.

  • The runner stays ubuntu-latest. The notice that it moves to Ubuntu 26 from 19 October 2026 remains until GitHub switches.

For reviewers

  • The release notes of every skipped major were read: Node 24 runtime; checkout v6 stores credentials in a separate file and v7 blocks fork checkouts for pull_request_target; setup-node v6 limits automatic caching to npm (cache: npm is set explicitly); setup-python v7 drops pip-install; upload-artifact v7 adds opt-in direct uploads; the docker majors remove deprecated inputs and env vars. None of these is used here.
  • Every input the workflows pass was checked against the new action.yml files; none is missing.
  • The actions' own runtime (Node 24) is chosen by the action authors and cannot be set to 26 from the workflow.
  • The Docker publish workflow only runs on tags, so its annotations clear with the next release; the docker-build job of this PR builds the image with node:26-alpine.
  • Locally the web tests and builds already run on Node 26.8.1.

🤖 Generated with Claude Code

k3mpaxl and others added 2 commits October 7, 2026 08:23
GitHub warns on every job that the actions target the deprecated Node.js 20
runtime (forced to Node 24). All actions move to their current major
versions, which run on Node 24: checkout, setup-python, setup-node and
upload-artifact v7; docker setup-buildx, setup-qemu and login v4,
build-push v7, metadata v6. None of the breaking changes of the skipped
majors affects the inputs these workflows use.

CI and the Docker frontend stage use Node.js 26 (current release, LTS from
late October 2026) instead of 22. The documented minimum stays Node.js 20+.
The runner stays ubuntu-latest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The import of 10,000 rows through REST is stored by the browser in 50
acknowledged chunks; on shared CI runners that sometimes takes longer than
the 10 s action timeout every API call inherits (failed on 6 and 7 October,
passed in the parallel runs). Only this call gets 60 s; the test's own limit
stays 120 s.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@k3mpaxl
k3mpaxl merged commit c3cd8d8 into main Oct 7, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant