Skip to content

Build assets with Node 24 in CI - #104

Merged
rbruhn merged 1 commit into
developmentfrom
103-build-assets-with-node-24-in-ci
Oct 12, 2026
Merged

rbruhn merged 1 commit into
developmentfrom
103-build-assets-with-node-24-in-ci

Conversation

@rbruhn

@rbruhn rbruhn commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Closes #103.

Builds the assets in CI with Node 24 instead of Node 20, which reached end of life in April 2026. BioSpex already uses Node 24.

Only node-version in .github/workflows/deploy-environment.yml changes. The servers don't run Node; it's only used to build the CSS and JS that the deploy uploads.

Checked locally: building development from a clean export (yarn install --frozen-lockfile and npm run production) with Node 22 and Node 24 gives byte-identical output, with the same size and SHA-256 hash for every CSS and JS file.

The pull request checks don't run the build, so the first development deploy after merging is the real test.

Node 20 reached end of life in April 2026. Node 22 and 24 builds produce byte-identical assets.
@rbruhn
rbruhn merged commit 0597b0f into development Oct 12, 2026
2 checks passed
@rbruhn
rbruhn deleted the 103-build-assets-with-node-24-in-ci branch October 12, 2026 02:11
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