Closed
Stabilize bzlmod lockfile CI check against stale lockfile state#118
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job for bzlmod-lockfile-check
Stabilize bzlmod lockfile CI check against stale lockfile state
Aug 9, 2026
|
The created documentation from the pull request is available at: docu-html |
masc2023
marked this pull request as ready for review
August 9, 2026 10:56
masc2023
approved these changes
Aug 9, 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.
Bugfix
Important
Use this template only for bugfixes that do not influence topics covered by contribution requests or improvements.
Caution
Make sure to submit your pull-request as Draft until you are ready to have it reviewed by the Committers.
Description
The failing
bzlmod-lock / bzlmod-lockfile-checkjob was caused by lockfile validation depending on a stale/fragile lockfile resolution path, which surfaced as extension-resolution failures and an out-of-dateMODULE.bazel.lock.This change aligns the lockfile check with current Bazel module resolution behavior and refreshes lockfile state used by CI.
bazelbuild/setup-bazelisk@v3.bazelversion,MODULE.bazel, andMODULE.bazel.lockbazel mod tidyfollowed bygit diff --exit-codeto assert committed lockfile parityMODULE.bazel.lockin sync with the resolved module graph expected by current dependencies/extensionsRelated ticket
Important
Please replace
[ISSUE-NUMBER]with the issue-number that tracks this bug fix. If there is no suchticket yet, create one via this issue template.