fix: pin Node.js and pnpm versions in codegen Dockerfile#1143
Merged
Conversation
|
jakubno
approved these changes
Feb 17, 2026
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.
Note
Low Risk
Build-environment-only changes; main risk is codegen differences or CI breakage due to the pinned Node/Python versions and new install method.
Overview
Updates the codegen build image to be more deterministic by pinning Node.js and pnpm versions and installing Node via the official tarball (with arch detection) instead of the NodeSource apt repo.
Also bumps the base runtime image from
python:3.9topython:3.10for the Python stage.Written by Cursor Bugbot for commit d279ec0. This will update automatically on new commits. Configure here.