Update dependency googletest to v1.15.2

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
googletest	git_repository	minor	release-1.11.0 -> v1.15.2

---

Release Notes

google/googletest (googletest)

v1.15.2

Compare Source

Release Notes

GoogleTest will not accept patches of new features to the v1.15.x branch.
We recommend building GoogleTest from the latest commit instead.
Exceptional critical bug fixes may be considered.

C++ Language Support

• GoogleTest requires at least C++14 and follows Google's Foundational C++ Support Policy. See this table for a list of currently supported versions compilers, platforms, and build tools.

Notable Changes

• Bzlmod is now officially supported (previously it was supported by the community). Note that it may take several days after the release for it to become available in the Bazel Central Registry.
• Many bug fixes

v1.15.0

Compare Source

Release Notes

GoogleTest will not accept patches of new features to the v1.15.x branch.
We recommend building GoogleTest from the latest commit instead.
Exceptional critical bug fixes may be considered.

C++ Language Support

• GoogleTest requires at least C++14 and follows Google's Foundational C++ Support Policy. See this table for a list of currently supported versions compilers, platforms, and build tools.

Notable Changes

• Bzlmod is now officially supported (previously it was supported by the community). Note that it may take several days after the release for it to become available in the Bazel Central Registry.
• Many bug fixes

Known Issues

• The Python toolchain in MODULE.bazel conflicts with downstream toolchains. This is fixed in 1.15.2.

v1.14.0

Compare Source

Release Notes

GoogleTest will not accept patches of new features to the v1.14.x branch.
We recommend building GoogleTest from the latest commit instead.
Exceptional critical bug fixes may be considered.

C++ Language Support

• GoogleTest requires at least C++14 and follows Google's Foundational C++ Support Policy. See this table for a list of currently supported versions compilers, platforms, and build tools.

Notable Changes

• Many bug fixes

v1.13.0

Compare Source

Release Notes

GoogleTest will not accept patches of new features to the v1.13.x branch.
We recommend building GoogleTest from the latest commit instead.
Exceptional critical bug fixes may be considered.

C++ Language Support

• GoogleTest now requires at least C++14 and follows Google's Foundational C++ Support Policy. See this table for a list of currently supported versions compilers, platforms, and build tools.

Notable Changes

• Floating point prints full precision by default to aid in debugging (google/googletest@9c33214)
• GTEST_FAIL_AT now terminates the test (like ASSERT_*), rather than failing and continuing (like EXPECT_*) (google/googletest@6f14952)
• Added testing::SrcDir(), which returns the configured directory for test data files (google/googletest@912db74)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Walkthrough

The update to the WORKSPACE file modifies the git_repository configuration for the googletest dependency. The tag has been upgraded from release-1.11.0 to v1.15.2, which signifies a transition to a newer version of the testing library. This change may enhance the project's stability and capabilities through the inclusion of recent bug fixes and features. Overall, it aims to improve the development experience by ensuring access to the latest improvements.

Changes

File(s)	Change Summary
WORKSPACE	Updated googletest dependency tag from release-1.11.0 to v1.15.2.

Poem

In the garden of code, with a hop and a cheer,
We’ve found a new version, let’s spread the good cheer!
From release-1.11.0, we leap to v1.15.2,
Bugs squashed, features sprouted, oh what joy anew!
With each little change, our tests will take flight,
A brighter, more stable coding delight! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 11b5dc3 and 084c7cb.

Files selected for processing (1)

• WORKSPACE (1 hunks)

Additional comments not posted (1)

WORKSPACE (1)

7-7: Verify compatibility with googletest v1.15.2.

The update to googletest from release-1.11.0 to v1.15.2 might introduce changes that affect test behavior or compatibility. Ensure that all tests pass and that there are no deprecated features or breaking changes impacting your project.