Skip to content

chore(deps): bump googletest from 1.17.0 to 1.17.0.bcr.2#54

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/bazel/googletest-1.17.0.bcr.2
Open

chore(deps): bump googletest from 1.17.0 to 1.17.0.bcr.2#54
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/bazel/googletest-1.17.0.bcr.2

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 23, 2026

Bumps googletest from 1.17.0 to 1.17.0.bcr.2.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [googletest](https://github.com/google/googletest) from 1.17.0 to 1.17.0.bcr.2.
- [Release notes](https://github.com/google/googletest/releases)
- [Commits](https://github.com/google/googletest/commits)

---
updated-dependencies:
- dependency-name: googletest
  dependency-version: 1.17.0.bcr.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added bazel Pull requests that update bazel code dependencies Pull requests that update a dependency file labels Mar 23, 2026
@github-actions
Copy link

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.3.0) and connecting to it...
INFO: Invocation ID: 6074de5f-90ee-4e3f-b060-cb132b6c4192
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'rules_python', the root module requires module version rules_python@1.4.1, but got rules_python@1.5.1 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: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

ERROR: Analysis of target '//:license-check' failed; build aborted: MODULE.bazel.lock is no longer up-to-date because: The implementation of the extension '@@rules_python+//python/uv:uv.bzl%uv' or one of its transitive .bzl files has changed,The usages of the extension '@@rules_python+//python/uv:uv.bzl%uv' have changed. Please run `bazel mod deps --lockfile_mode=update` to update your lockfile.
INFO: Elapsed time: 10.441s, Critical Path: 0.03s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully
FAILED: 
ERROR: Build failed. Not running target

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bazel Pull requests that update bazel code dependencies Pull requests that update a dependency file

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

0 participants