Repository navigation
chore: upgrade the front to Node 26 on Alpine - #216
Merged
Merged
Conversation
- front/Dockerfile: node:22-alpine -> node:26-alpine3.24 (build and runtime) - deploy-front.yml: checkout@v7, login-action@v4, setup-buildx-action@v4 and build-push-action@v7 (node24 runtimes) - ci.yml: Node 20.x -> 26.x, checkout@v7 and setup-node@v7 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.
Summary
Node 22 reaches end of life on 30/04/2027, so this moves the front (
info-embalse-front-prod) to Node 26 LTS.node:22-alpine→node:26-alpine3.24in the builder and runner stages.node24majors:actions/checkout@v7,docker/login-action@v4,docker/setup-buildx-action@v4,docker/build-push-action@v7(azure/webapps-deploy@v3already runs onnode24).20.x→26.x,actions/checkout@v7,actions/setup-node@v7.The Azure Function (
fn-info-embalse-prod,deploy-functions.yml) is not touched here: Azure Functions doesn't offer Node 26 yet, so it will move to Node 24 in a separate PR after the runtime is changed in the portal.Local verification
docker buildx build --platform linux/amd64 -f front/Dockerfile .on Node 26.13.0 / Alpine 3.24.3: OK.turbo type-check22/22 tasks,npm run test9 files / 73 tests passed.Notes (not changed here)
@tailwindcss/oxide-linux-x64-musl, so it only builds on x64 (fails on arm64 machines). The lockfile already includes the musl binaries, and thepackageManagerremoval was for Corepack, which Node 26 no longer ships; both workarounds could probably be dropped.generateMetadatalogsCannot read properties of null (reading 'nombre')(the page still returns 404).Merging deploys to
info-embalse-front-prod.🤖 Generated with Claude Code