Skip to content

Stabilize bzlmod lockfile CI check against stale lockfile state - #118

Closed
masc2023 with Copilot wants to merge 1 commit into
mainfrom
copilot/fix-bzlmod-lockfile-check-again
Closed

Stabilize bzlmod lockfile CI check against stale lockfile state#118
masc2023 with Copilot wants to merge 1 commit into
mainfrom
copilot/fix-bzlmod-lockfile-check-again

Conversation

Copilot AI commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

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-check job was caused by lockfile validation depending on a stale/fragile lockfile resolution path, which surfaced as extension-resolution failures and an out-of-date MODULE.bazel.lock.
This change aligns the lockfile check with current Bazel module resolution behavior and refreshes lockfile state used by CI.

  • Workflow hardening
    • Use bazelbuild/setup-bazelisk@v3
    • Cache Bazel artifacts with key material including .bazelversion, MODULE.bazel, and MODULE.bazel.lock
  • Lockfile validation behavior
    • Validate with bazel mod tidy followed by git diff --exit-code to assert committed lockfile parity
  • Repository state alignment
    • Keep MODULE.bazel.lock in sync with the resolved module graph expected by current dependencies/extensions
- name: Check lockfile is up to date
  run: |
    bazel mod tidy
    git diff --exit-code

Related ticket

Important

Please replace [ISSUE-NUMBER] with the issue-number that tracks this bug fix. If there is no such
ticket yet, create one via this issue template.

@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: d58b0fcd-fd3a-4b73-8564-d2f8084368ee
Computing main repo mapping: 
Computing main repo mapping: 
DEBUG: Rule 'rules_boost+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-LTilyiMMjpYyAi1PW+8RycyAEHy9clo7915R0Bchb2E="
DEBUG: Repository rules_boost+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:394:31: in <toplevel>
WARNING: For repository 'score_bazel_platforms', the root module requires module version score_bazel_platforms@0.1.1, but got score_bazel_platforms@0.1.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'googletest', the root module requires module version googletest@1.17.0, but got googletest@1.17.0.bcr.2 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 4 packages loaded
Loading: 4 packages loaded
    currently loading: 
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/feo/feo/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/feo/feo/BUILD
INFO: Elapsed time: 6.647s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

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
Copilot AI requested a review from masc2023 August 9, 2026 09:45
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown

The created documentation from the pull request is available at: docu-html

@masc2023
masc2023 marked this pull request as ready for review August 9, 2026 10:56
@masc2023 masc2023 closed this Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants