Skip to content

v1.13.0 Release

Choose a tag to compare

@coryan coryan released this 01 May 15:36
7ea2b7a

NOTICE: This release aligns all the version numbers for Bigtable, Storage,
the common libraries, and the repository itself. From this point on all
releases will include a single version number. Note that there is a gap in the
version numbers for Bigtable and the repository changes from v0.21.0 to
v1.13.0

BREAKING CHANGES

  • The common library inlined namespace changed to v0 to v1, moving all the
    symbols from google::cloud::v0 to google::cloud::v1. Applications that
    explicitly referred to the inlined namespace would be affected by this change.
    That is, code that uses google::cloud::v0::Foo instead of
    google::cloud::Foo would need to be modified. We apologize if this has
    impacted you, and recommend that applications do not refer to the inlined
    namespace in the future.

Bigtable

BREAKING CHANGES

See above regarding the common library inlined namespace.

OTHER CHANGES

  • cleanup: the library now links against the common libraries included in this
    repository, applications developers should not install the standalone common
    libraries in the (now archived) google-cloud-cpp-common repository.
  • feat: compile bigtable benchmarks with Bazel (#3884)
  • feat: implement table level IAM policy for bigtable(async) (#3829)
  • feat: implement table level IAM policy for bigtable (#3751)
  • refactor: synchronize version numbers for all libraries (#3710)
  • feat: change READMEs and quickstart programs (#3690)
    The google/cloud/bigable/quickstart/ directory contains a sample project
    for CMake and Bazel that uses the Cloud Bigtable C++ client library as we
    expect application developers would.

Storage

BREAKING CHANGES

See above regarding the common library inlined namespace.

  • fix!: use correct type for generation numbers (#3870) This changes the type of
    two fields from google::cloud::optional<long> to
    google::cloud::optional<std::int64_t>. With MSVC this is not a backwards
    compatible change (storing the result of .value() into a long now loses
    precision). However, on that platform the fields were not usable, they could
    not store the values that are typically generated by the production
    environment. We apologize to any customers affected by this change, but we
    think it is unlikely that anybody used the field on that platform.

OTHER CHANGES

  • cleanup: the library now links against the common libraries included in this
    repository, applications developers should not install the standalone common
    libraries in the (now archived) google-cloud-cpp-common repository.
  • feat: implement POST policy signatures. Applications can use the Google Cloud
    Storage C++ client library to create
    POST objects,
    which allow uploading using HTML forms.
  • feat: change READMEs and quickstart programs (#3690)
    The google/cloud/bigable/quickstart/ directory contains a sample project
    for CMake and Bazel that uses the Cloud Bigtable C++ client library as we
    expect application developers would.
  • fix: use network to check if running inside Google (#3959) With this change
    applications running on Google App Engine Flex (GAEF), Google Kubernetes
    Engine (GKE), or Cloud Run can use the Google Default Credentials.
  • fix: build problems on MSVC x86 (#3916)
  • fix: do not use CURL_SHARE features (#3860)
  • chore: upgrade libcurl to v7.69.1 (#3851)

Common Libraries

BREAKING CHANGES

See above regarding the common library inlined namespace.

OTHER CHANGES

No other interesting changes in the common libraries with this release.