Repository navigation
Upgrade Node.js to stable 26.12.1 - #370
Merged
Merged
Conversation
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.
Changes
.nvmrcand use it for tests, Pages deployment and version preparation..nvmrc.node:26.12.1-bookworm-slim.>=22.22.0supported minimum and leave manifests and lockfiles unchanged. Installed React and React DOM are already the latest stable 19.3.1.Verification
All local commands used the checksum-verified Node.js 26.12.1 runtime with npm 11.20.0.
actionlint.--no-cache; the isolated Porto stack passed explicit backend health and frontend HTTP probes. Porto does not expose Docker health metadata, so the local scratch override usedservice_startedplus explicit probes. Production Compose healthchecks are unchanged. All owned containers, volumes, networks and image tags were removed afterward.Local macOS packaging used the repository's ad-hoc signing fallback because no Developer ID certificate is configured.
Scope
Latest stable releases were verified against the official Node.js distribution index and npm React/React DOM metadata on 2026-10-25. This repository has no Next.js, Go or Java application runtime. Python is used only through runner-provided release metadata helpers and an optional static-file preview command, with no separately managed application runtime to upgrade. No unrelated dependencies, application behavior or financial/storage semantics changed.