Repository navigation
CI on Node 24 actions; Node.js 26 for CI and the frontend image - #7
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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
pull_request_target; setup-node v6 limits automatic caching to npm (cache: npmis set explicitly); setup-python v7 dropspip-install; upload-artifact v7 adds opt-in direct uploads; the docker majors remove deprecated inputs and env vars. None of these is used here.action.ymlfiles; none is missing.docker-buildjob of this PR builds the image withnode:26-alpine.🤖 Generated with Claude Code