Repository navigation
fix: pin score_devcontainer to 1.11.2 (1.11.1 yanked upstream) - #81
Merged
michaelsaborov merged 1 commit intoOct 15, 2026
Merged
Conversation
Chahult
requested review from
LittleHuba,
antonkri,
castler,
michaelsaborov and
ramceb
as code owners
October 15, 2026 06:49
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
michaelsaborov
approved these changes
Oct 15, 2026
This branch was successfully 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.
As we are using the QNX YAML configuration from Logging, and Logging is not affected, we confirmed that
score_devcontainerdoes not appear anywhere inMODULE.bazel.lock.Our analysis: Logging pins
score_tooling@1.2.0, which is much older than Config Management'sscore_tooling@2.2.1. The transitive dependency onscore_devcontainerwas apparently introduced in a newer release line (2.x) that Logging does not use yet. As a result, Logging's dependency graph does not resolve or fetchscore_devcontainer, so the issue with the yanked1.11.1version does not apply to Logging.