chore(deps): update dependency google_cloud_cpp to v2.27.0 #14603
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.26.0
->v2.27.0
Release Notes
googleapis/google-cloud-cpp (google_cloud_cpp)
v2.27.0
Compare Source
We now link our mocking libraries against GoogleTest in CMake.
The mocking libraries require GoogleTest. Not linking GoogleTest was a bug.
This bug surfaced in versions of CMake >= 3.30.
Note that the mocking libraries are built by default. If you want to opt-out
of building or installing the mocking libraries, you can supply
-DGOOGLE_CLOUD_CPP_WITH_MOCKS=OFF
to your CMake configure command.If your build fails because GoogleTest is not found, supply
-DGOOGLE_CLOUD_CPP_WITH_MOCKS=OFF
as mentioned above.We have stopped testing on CentOS 7, Debian 10 (Buster), and RockyLinux 8 as
these distros are EOL or in some form of "security only" support period.
Note that we used CentOS 7 as a proxy for testing RedHat Enterprise Linux 7.
BREAKING TESTING CHANGES
If you don't mock Long Running Operations (LRO) in your tests, then these
changes will not affect you.
With the promotion from Experimental to GA of the new methods to support
starting Long Running Operations (LRO) synchronously and awaiting their
completion separately, the use of
ExperimentalTag
is no longer required. Theoverload set for LRO methods has changed and may require matchers to
disambiguate invocations of
EXPECT_CALL
(https://google.github.io/googletest/gmock_cook_book.html#SelectOverload).
New Libraries
We are happy to announce the following GA libraries. Unless specifically noted,
the APIs in these libraries are stable, and are ready for production use.
The following experimental libraries are now available:
This library provides support for the Dataset, Job, Model, Project, Routine,
RowAccessPolicy, and Table REST resources.
OpenTelemetry
Bazel
The
--io_opentelemetry_cpp//api:with_abseil
flag was marked as deprecated inOpenTelemetry v1.16.0. It may be removed in future versions.
In previous versions of
opentelemetry-cpp
, this flag was required forcompatibility with Abseil. It is no longer necessary, as
opentelemetry-cpp
iscompiled with Abseil by default.
We have stopped using the flag to validate Bazel build configurations with
OpenTelemetry tracing enabled.
If you are building
google-cloud-cpp
withopentelemetry-cpp
< v1.16.0, youwill need to supply the flag for compatibility with Abseil. The following can be
added to your
.bazelrc
file.Spanner
Storage
ReadObject()
(#14435)Common Libraries
function call, and then await the LRO to complete on a separate function.
json_fwd.h
is not always available (#14439)Configuration
📅 Schedule: Branch creation - "every weekday" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.
This change is