Compare commits

...
1 Commits
Author SHA1 Message Date
Prashant Kumar 063de7e957 Prepare for v1.18.0 (#5055) 2026-08-10 13:19:17 -04:00
4 changed files with 6 additions and 6 deletions
+1 -1
View File
@@ -32,7 +32,7 @@
module(
name = "googletest",
version = "head",
version = "1.18.0",
compatibility_level = 1,
)
+3 -3
View File
@@ -8,12 +8,12 @@ Our documentation is now live on GitHub Pages at
https://google.github.io/googletest/. We recommend browsing the documentation on
GitHub Pages rather than directly in the repository.
#### Release 1.17.0
#### Release 1.18.0
[Release 1.17.0](https://github.com/google/googletest/releases/tag/v1.17.0) is
[Release 1.18.0](https://github.com/google/googletest/releases/tag/v1.18.0) is
now available.
The 1.17.x branch
The 1.18.x branch
[requires at least C++17](https://opensource.google/documentation/policies/cplusplus-support#c_language_standard).
#### Continuous Integration
+1 -1
View File
@@ -48,7 +48,7 @@ with the following content:
# Choose the most recent version available at
# https://registry.bazel.build/modules/googletest
bazel_dep(name = "googletest", version = "1.17.0")
bazel_dep(name = "googletest", version = "1.18.0")
```
Now you're ready to build C++ code that uses GoogleTest.
+1 -1
View File
@@ -25,7 +25,7 @@ When building GoogleTest as a standalone project, the typical workflow starts
with
```
git clone https://github.com/google/googletest.git -b v1.17.0
git clone https://github.com/google/googletest.git -b v1.18.0
cd googletest # Main directory of the cloned repository.
mkdir build # Create a directory to hold the build output.
cd build