Repository navigation
Pin the container preview to Node 22 and document local setup with corepack - #891
Open
bennyvasquez wants to merge 1 commit into
Open
bennyvasquez wants to merge 1 commit into
bennyvasquez wants to merge 1 commit into
Conversation
…repack The Containerfile used node:lts-alpine for both stages, so the container preview could drift from the Node 22 the deploy workflow uses. Both stages now use node:22-alpine. The image builds, and the dev server starts and serves the wiki on Node 22.23.5. The contributor guide's local setup now says to use Node.js 22 on every operating system and to turn on yarn 1 with corepack enable, which ships with Node.js 22. With no packageManager field in package.json, corepack provides yarn 1.22.22, which matches the yarn.lock format the deploy installs from.
bennyvasquez
marked this pull request as ready for review
November 16, 2026 18:35
This branch has not been deployed
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.
This follows up on the README and deploy docs PR that merged last week. It makes the two local preview paths match what the deploy uses.
What changes
node:22-alpineinstead ofnode:lts-alpine. The LTS tag will move off Node 22, and when it does, the container preview would stop matching the deploy workflow, which pins Node 22.corepack enable, then run the existingyarn installandyarn docs:devsteps. It replaces the old tip that only mentioned installing Node.js on Windows and macOS.How I tested it
corepack enableinnode:22-alpinewith this repo'spackage.json. Since there's nopackageManagerfield, corepack provides yarn 1.22.22, which matches the yarn 1 lock file the deploy installs from.Something I'd like a second opinion on
The guide says you can install Node.js 22 from your operating system's package manager. I haven't confirmed that every distribution's Node.js package includes corepack, since some split it into a separate package. If you know of one where
corepackis missing, tell me and I'll add a line about it.