Repository navigation
Fix node-packages Debian test and use node feature v2 in tests - #33
Merged
Merged
Conversation
shokkunrf
force-pushed
the
features/node-packages/pin-test-node
branch
2 times, most recently
from
November 6, 2026 11:20
025d175 to
83dcb53
Compare
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
official-debianscenario. The node feature's defaultltsnow installs Node.js 26 (LTS since 2026-10-28), and Node.js 25+ needslibatomic.so.1, whichdebian:trixiedoes not ship and the node feature does not install, so the scenario failed witherror while loading shared libraries: libatomic.so.1shokkunrf-basescenario, whose base image haslibatomic1scenarios.jsoncomment to drop the pin once the Node.js LTS no longer needslibatomic1(nodejs/node#63270, which links it statically, for nodejs/node#60790). The devcontainer CLI parsesscenarios.jsonas JSONC, so comments are accepted:1to:2, matching the base image. v1 stopped at 1.7.1 and does not get v2 fixes (non-root pnpm install, Yarn APT keyring refresh)This failure blocks #30, which triggers the node-packages tests by touching its README.