Skip to content

Stabilize bzlmod lockfile check by pinning reusable workflow revision - #114

Closed
masc2023 with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-bzlmod-lockfile-check
Closed

Stabilize bzlmod lockfile check by pinning reusable workflow revision#114
masc2023 with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-bzlmod-lockfile-check

Conversation

Copilot AI commented Jul 31, 2026

Copy link
Copy Markdown

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 bzlmod-lock / bzlmod-lockfile-check job failed after the reusable workflow reference tracked @main and picked up upstream behavior changes.
This change removes that drift by pinning the workflow to the last known-good revision used by this repository.

  • What changed

    • Updated .github/workflows/bzlmod-lock.yml to reference a fixed commit SHA instead of @main.
  • Why this addresses the failure

    • Prevents unreviewed upstream workflow updates from changing lockfile-check behavior in this repo.
    • Restores deterministic CI execution for the bzlmod lockfile check.
  • Patch

    jobs:
      bzlmod-lock:
        uses: eclipse-score/cicd-workflows/.github/workflows/bzlmod-lock-check.yml@39939c97ac17f9e262860cf325bdd52d4a2d21a5

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.

Copilot AI changed the title [WIP] Fix failing GitHub Actions job for bzlmod-lockfile-check Stabilize bzlmod lockfile check by pinning reusable workflow revision Jul 31, 2026
Copilot AI requested a review from masc2023 July 31, 2026 14:43
@github-actions

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: 35a58ea8-1ce4-4bee-80ce-f748971cd4ac
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: 
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.847s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@github-actions

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 2, 2026 11:03
@masc2023
masc2023 self-requested a review August 2, 2026 11:06
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