Skip to content
This repository was archived by the owner on May 14, 2026. It is now read-only.
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: googleapis/sdk-platform-java
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.21.0
Choose a base ref
...
head repository: googleapis/sdk-platform-java
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.22.0
Choose a head ref
  • 15 commits
  • 66 files changed
  • 7 contributors

Commits on Jun 6, 2023

  1. chore(main): release 2.21.1-SNAPSHOT (#1758)

    Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
    release-please[bot] authored Jun 6, 2023
    Configuration menu
    Copy the full SHA
    97cd3b7 View commit details
    Browse the repository at this point in the history

Commits on Jun 8, 2023

  1. feat: dynamically determine protobuf version in build.gradle (#1753)

    * feat: dynamically determine protobuf version in build.gradle
    
    * add code comment
    
    * add a method to sync versions from googleapis
    
    * add a seperate dict for synced version
    
    * restore protobuf version in dependencies.properties
    
    * add synced version after reading properties
    
    * combine two properties
    
    * remove protobuf version in dependencies.properties
    
    * empty commit
    
    * Revert "remove protobuf version in dependencies.properties"
    
    This reverts commit 22d3d0c.
    
    * add comment for protobuf version
    
    * make a copy of properties
    
    * change comment
    
    * change comments
    JoeWang1127 authored Jun 8, 2023
    Configuration menu
    Copy the full SHA
    6de5110 View commit details
    Browse the repository at this point in the history

Commits on Jun 9, 2023

  1. Configuration menu
    Copy the full SHA
    dfa9d2b View commit details
    Browse the repository at this point in the history

Commits on Jun 12, 2023

  1. chore: Clean up resources in gRPCStreamDirectController and ChannelPo…

    …ol tests (#1691)
    
    * chore: Shutdown test resources
    
    * chore: Clean up resources for the flaky test
    
    * chore: Clean up test
    
    * chore: Shutdown ChannelPool resources
    
    * chore: Use constant for termination seconds
    
    * chore: Clean up exception in runnable
    
    * chore: Increase termination delay
    
    * chore: Clean up resources
    
    * chore: Clean up resources after tests
    lqiu96 authored Jun 12, 2023
    Configuration menu
    Copy the full SHA
    8cbea70 View commit details
    Browse the repository at this point in the history

Commits on Jun 16, 2023

  1. Configuration menu
    Copy the full SHA
    a8f7999 View commit details
    Browse the repository at this point in the history

Commits on Jun 19, 2023

  1. build(deps): bump guava from 31.1-jre to 32.0.0-jre in /java-common-p…

    …rotos (#1776)
    
    Bumps [guava](https://togithub.com/google/guava) from 31.1-jre to 32.0.0-jre.
    <details>
    <summary>Release notes</summary>
    <p><em>Sourced from <a href="https://togithub.com/google/guava/releases">guava's releases</a>.</em></p>
    <blockquote>
    <h2>32.0.0</h2>
    <h3>Maven</h3>
    <pre lang="xml"><code>&lt;dependency&gt;
      &lt;groupId&gt;com.google.guava&lt;/groupId&gt;
      &lt;artifactId&gt;guava&lt;/artifactId&gt;
      &lt;version&gt;32.0.0-jre&lt;/version&gt;
      &lt;!-- or, for Android: --&gt;
      &lt;version&gt;32.0.0-android&lt;/version&gt;
    &lt;/dependency&gt;
    </code></pre>
    <h3>Jar files</h3>
    <ul>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.jar">32.0.0-jre.jar</a></li>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/guava/32.0.0-android/guava-32.0.0-android.jar">32.0.0-android.jar</a></li>
    </ul>
    <p>Guava requires <a href="https://togithub.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies">one runtime dependency</a>, which you can download here:</p>
    <ul>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar">failureaccess-1.0.1.jar</a></li>
    </ul>
    <h3>Javadoc</h3>
    <ul>
    <li><a href="http://guava.dev/releases/32.0.0-jre/api/docs/">32.0.0-jre</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/docs/">32.0.0-android</a></li>
    </ul>
    <h3>JDiff</h3>
    <ul>
    <li><a href="http://guava.dev/releases/32.0.0-jre/api/diffs/">32.0.0-jre vs. 31.1-jre</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/diffs/">32.0.0-android vs. 31.1-android</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/androiddiffs/">32.0.0-android vs. 32.0.0-jre</a></li>
    </ul>
    <h3>Changelog</h3>
    <h4>Security fixes</h4>
    <ul>
    <li>Reimplemented <code>Files.createTempDir</code> and <code>FileBackedOutputStream</code> to further address CVE-2020-8908 (<a href="https://redirect.github.com/google/guava/issues/4011">#4011</a>) and CVE-2023-2976 (<a href="https://redirect.github.com/google/guava/issues/2575">#2575</a>). (feb83a1c8f)</li>
    </ul>
    <p>While CVE-2020-8908 was officially closed when we deprecated <code>Files.createTempDir</code> in <a href="https://togithub.com/google/guava/releases/tag/v30.0">Guava 30.0</a>, we've heard from users that even recent versions of Guava have been listed as vulnerable in <em>other</em> databases of security vulnerabilities. In response, we've reimplemented the method (and the very rarely used <code>FileBackedOutputStream</code> class, which had a similar issue) to eliminate the insecure behavior entirely. This change could technically affect users in a number of different ways (discussed under &quot;Incompatible changes&quot; below), but in practice, the only problem users are likely to encounter is with Windows. If you are using those APIs under Windows, you should skip 32.0.0 and go straight to <a href="https://togithub.com/google/guava/releases/tag/v32.0.1">32.0.1</a> which fixes the problem. (Unfortunately, we didn't think of the Windows problem until after the release. And while we <a href="https://togithub.com/google/guava#important-warnings">warn that <code>common.io</code> in particular may not work under Windows</a>, we didn't intend to regress support.) Sorry for the trouble.</p>
    <h4>Incompatible changes</h4>
    <p>Although this release bumps Guava's major version number, it makes <strong>no binary-incompatible changes to the <code>guava</code> artifact</strong>.</p>
    <p>One change could cause issues for Widows users, and a few other changes could cause issues for users in more usual situations:</p>
    <ul>
    <li><strong>The new implementations of <code>Files.createTempDir</code> and <code>FileBackedOutputStream</code> <a href="https://redirect.github.com/google/guava/issues/6535">throw an exception under Windows</a>.</strong> This is fixed in <a href="https://togithub.com/google/guava/releases/tag/v32.0.1">32.0.1</a>. Sorry for the trouble.</li>
    <li>This release makes a binary-incompatible change to a <code>@beta</code> API in the <strong>separate artifact</strong> <code>guava-testlib</code>. Specifically, we changed the return type of <code>TestingExecutors.sameThreadScheduledExecutor</code> to <code>ListeningScheduledExecutorService</code>. The old return type was a package-private class, which caused the Kotlin compiler to produce warnings. (dafaa3e435)</li>
    <li>This release <em>adds</em> two methods to the Android flavor of Guava: <code>Invokable.getAnnotatedReturnType()</code> and <code>Parameter.getAnnotatedType()</code>. Those methods do not work under an Android VM; we added them only to help our tests of the Android flavor (since we also run those tests under a JRE). Android VMs tolerate such methods as long as the app does not call them or perform reflection on them, and builds tolerate them because of our new Proguard configurations (discussed below). Thus, we expect no impact to most users. However, we could imagine build problems for users who have set up their own build system for the Android flavor of Guava. Please report any problems so that we can judge how safely we might be able to add other methods to the Android flavor in the future, such as APIs that use Java 8 classes like <code>Stream</code>. (b30e73cfa81ad15c1023c17cfd083255a3df0105)</li>
    </ul>
    <!-- raw HTML omitted -->
    </blockquote>
    <p>... (truncated)</p>
    </details>
    <details>
    <summary>Commits</summary>
    <ul>
    <li>See full diff in <a href="https://togithub.com/google/guava/commits">compare view</a></li>
    </ul>
    </details>
    <br />
    
    
    [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.google.guava:guava&package-manager=maven&previous-version=31.1-jre&new-version=32.0.0-jre)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
    
    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-automerge-start)
    [//]: # (dependabot-automerge-end)
    
    ---
    
    <details>
    <summary>Dependabot commands and options</summary>
    <br />
    
    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 merge` will merge this PR after your CI passes on it
    - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
    - `@dependabot cancel merge` will cancel a previously requested merge and block automerging
    - `@dependabot reopen` will reopen this PR if it is closed
    - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    - `@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)
    You can disable automated security fix PRs for this repo from the [Security Alerts page](https://togithub.com/googleapis/sdk-platform-java/network/alerts).
    
    </details>
    dependabot[bot] authored Jun 19, 2023
    Configuration menu
    Copy the full SHA
    e0c2b45 View commit details
    Browse the repository at this point in the history
  2. build(deps): bump guava from 31.1-jre to 32.0.0-jre in /gapic-generat…

    …or-java (#1775)
    
    Bumps [guava](https://togithub.com/google/guava) from 31.1-jre to 32.0.0-jre.
    <details>
    <summary>Release notes</summary>
    <p><em>Sourced from <a href="https://togithub.com/google/guava/releases">guava's releases</a>.</em></p>
    <blockquote>
    <h2>32.0.0</h2>
    <h3>Maven</h3>
    <pre lang="xml"><code>&lt;dependency&gt;
      &lt;groupId&gt;com.google.guava&lt;/groupId&gt;
      &lt;artifactId&gt;guava&lt;/artifactId&gt;
      &lt;version&gt;32.0.0-jre&lt;/version&gt;
      &lt;!-- or, for Android: --&gt;
      &lt;version&gt;32.0.0-android&lt;/version&gt;
    &lt;/dependency&gt;
    </code></pre>
    <h3>Jar files</h3>
    <ul>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.jar">32.0.0-jre.jar</a></li>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/guava/32.0.0-android/guava-32.0.0-android.jar">32.0.0-android.jar</a></li>
    </ul>
    <p>Guava requires <a href="https://togithub.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies">one runtime dependency</a>, which you can download here:</p>
    <ul>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar">failureaccess-1.0.1.jar</a></li>
    </ul>
    <h3>Javadoc</h3>
    <ul>
    <li><a href="http://guava.dev/releases/32.0.0-jre/api/docs/">32.0.0-jre</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/docs/">32.0.0-android</a></li>
    </ul>
    <h3>JDiff</h3>
    <ul>
    <li><a href="http://guava.dev/releases/32.0.0-jre/api/diffs/">32.0.0-jre vs. 31.1-jre</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/diffs/">32.0.0-android vs. 31.1-android</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/androiddiffs/">32.0.0-android vs. 32.0.0-jre</a></li>
    </ul>
    <h3>Changelog</h3>
    <h4>Security fixes</h4>
    <ul>
    <li>Reimplemented <code>Files.createTempDir</code> and <code>FileBackedOutputStream</code> to further address CVE-2020-8908 (<a href="https://redirect.github.com/google/guava/issues/4011">#4011</a>) and CVE-2023-2976 (<a href="https://redirect.github.com/google/guava/issues/2575">#2575</a>). (feb83a1c8f)</li>
    </ul>
    <p>While CVE-2020-8908 was officially closed when we deprecated <code>Files.createTempDir</code> in <a href="https://togithub.com/google/guava/releases/tag/v30.0">Guava 30.0</a>, we've heard from users that even recent versions of Guava have been listed as vulnerable in <em>other</em> databases of security vulnerabilities. In response, we've reimplemented the method (and the very rarely used <code>FileBackedOutputStream</code> class, which had a similar issue) to eliminate the insecure behavior entirely. This change could technically affect users in a number of different ways (discussed under &quot;Incompatible changes&quot; below), but in practice, the only problem users are likely to encounter is with Windows. If you are using those APIs under Windows, you should skip 32.0.0 and go straight to <a href="https://togithub.com/google/guava/releases/tag/v32.0.1">32.0.1</a> which fixes the problem. (Unfortunately, we didn't think of the Windows problem until after the release. And while we <a href="https://togithub.com/google/guava#important-warnings">warn that <code>common.io</code> in particular may not work under Windows</a>, we didn't intend to regress support.) Sorry for the trouble.</p>
    <h4>Incompatible changes</h4>
    <p>Although this release bumps Guava's major version number, it makes <strong>no binary-incompatible changes to the <code>guava</code> artifact</strong>.</p>
    <p>One change could cause issues for Widows users, and a few other changes could cause issues for users in more usual situations:</p>
    <ul>
    <li><strong>The new implementations of <code>Files.createTempDir</code> and <code>FileBackedOutputStream</code> <a href="https://redirect.github.com/google/guava/issues/6535">throw an exception under Windows</a>.</strong> This is fixed in <a href="https://togithub.com/google/guava/releases/tag/v32.0.1">32.0.1</a>. Sorry for the trouble.</li>
    <li>This release makes a binary-incompatible change to a <code>@beta</code> API in the <strong>separate artifact</strong> <code>guava-testlib</code>. Specifically, we changed the return type of <code>TestingExecutors.sameThreadScheduledExecutor</code> to <code>ListeningScheduledExecutorService</code>. The old return type was a package-private class, which caused the Kotlin compiler to produce warnings. (dafaa3e435)</li>
    <li>This release <em>adds</em> two methods to the Android flavor of Guava: <code>Invokable.getAnnotatedReturnType()</code> and <code>Parameter.getAnnotatedType()</code>. Those methods do not work under an Android VM; we added them only to help our tests of the Android flavor (since we also run those tests under a JRE). Android VMs tolerate such methods as long as the app does not call them or perform reflection on them, and builds tolerate them because of our new Proguard configurations (discussed below). Thus, we expect no impact to most users. However, we could imagine build problems for users who have set up their own build system for the Android flavor of Guava. Please report any problems so that we can judge how safely we might be able to add other methods to the Android flavor in the future, such as APIs that use Java 8 classes like <code>Stream</code>. (b30e73cfa81ad15c1023c17cfd083255a3df0105)</li>
    </ul>
    <!-- raw HTML omitted -->
    </blockquote>
    <p>... (truncated)</p>
    </details>
    <details>
    <summary>Commits</summary>
    <ul>
    <li>See full diff in <a href="https://togithub.com/google/guava/commits">compare view</a></li>
    </ul>
    </details>
    <br />
    
    
    [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.google.guava:guava&package-manager=maven&previous-version=31.1-jre&new-version=32.0.0-jre)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
    
    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-automerge-start)
    [//]: # (dependabot-automerge-end)
    
    ---
    
    <details>
    <summary>Dependabot commands and options</summary>
    <br />
    
    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 merge` will merge this PR after your CI passes on it
    - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
    - `@dependabot cancel merge` will cancel a previously requested merge and block automerging
    - `@dependabot reopen` will reopen this PR if it is closed
    - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    - `@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)
    You can disable automated security fix PRs for this repo from the [Security Alerts page](https://togithub.com/googleapis/sdk-platform-java/network/alerts).
    
    </details>
    dependabot[bot] authored Jun 19, 2023
    Configuration menu
    Copy the full SHA
    65bc13f View commit details
    Browse the repository at this point in the history
  3. build(deps-dev): bump guava from 31.0.1-jre to 32.0.0-jre in /java-sh…

    …ared-dependencies/dependency-convergence-check (#1774)
    
    Bumps [guava](https://togithub.com/google/guava) from 31.0.1-jre to 32.0.0-jre.
    <details>
    <summary>Release notes</summary>
    <p><em>Sourced from <a href="https://togithub.com/google/guava/releases">guava's releases</a>.</em></p>
    <blockquote>
    <h2>32.0.0</h2>
    <h3>Maven</h3>
    <pre lang="xml"><code>&lt;dependency&gt;
      &lt;groupId&gt;com.google.guava&lt;/groupId&gt;
      &lt;artifactId&gt;guava&lt;/artifactId&gt;
      &lt;version&gt;32.0.0-jre&lt;/version&gt;
      &lt;!-- or, for Android: --&gt;
      &lt;version&gt;32.0.0-android&lt;/version&gt;
    &lt;/dependency&gt;
    </code></pre>
    <h3>Jar files</h3>
    <ul>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/guava/32.0.0-jre/guava-32.0.0-jre.jar">32.0.0-jre.jar</a></li>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/guava/32.0.0-android/guava-32.0.0-android.jar">32.0.0-android.jar</a></li>
    </ul>
    <p>Guava requires <a href="https://togithub.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies">one runtime dependency</a>, which you can download here:</p>
    <ul>
    <li><a href="https://repo1.maven.org/maven2/com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar">failureaccess-1.0.1.jar</a></li>
    </ul>
    <h3>Javadoc</h3>
    <ul>
    <li><a href="http://guava.dev/releases/32.0.0-jre/api/docs/">32.0.0-jre</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/docs/">32.0.0-android</a></li>
    </ul>
    <h3>JDiff</h3>
    <ul>
    <li><a href="http://guava.dev/releases/32.0.0-jre/api/diffs/">32.0.0-jre vs. 31.1-jre</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/diffs/">32.0.0-android vs. 31.1-android</a></li>
    <li><a href="http://guava.dev/releases/32.0.0-android/api/androiddiffs/">32.0.0-android vs. 32.0.0-jre</a></li>
    </ul>
    <h3>Changelog</h3>
    <h4>Security fixes</h4>
    <ul>
    <li>Reimplemented <code>Files.createTempDir</code> and <code>FileBackedOutputStream</code> to further address CVE-2020-8908 (<a href="https://redirect.github.com/google/guava/issues/4011">#4011</a>) and CVE-2023-2976 (<a href="https://redirect.github.com/google/guava/issues/2575">#2575</a>). (feb83a1c8f)</li>
    </ul>
    <p>While CVE-2020-8908 was officially closed when we deprecated <code>Files.createTempDir</code> in <a href="https://togithub.com/google/guava/releases/tag/v30.0">Guava 30.0</a>, we've heard from users that even recent versions of Guava have been listed as vulnerable in <em>other</em> databases of security vulnerabilities. In response, we've reimplemented the method (and the very rarely used <code>FileBackedOutputStream</code> class, which had a similar issue) to eliminate the insecure behavior entirely. This change could technically affect users in a number of different ways (discussed under &quot;Incompatible changes&quot; below), but in practice, the only problem users are likely to encounter is with Windows. If you are using those APIs under Windows, you should skip 32.0.0 and go straight to <a href="https://togithub.com/google/guava/releases/tag/v32.0.1">32.0.1</a> which fixes the problem. (Unfortunately, we didn't think of the Windows problem until after the release. And while we <a href="https://togithub.com/google/guava#important-warnings">warn that <code>common.io</code> in particular may not work under Windows</a>, we didn't intend to regress support.) Sorry for the trouble.</p>
    <h4>Incompatible changes</h4>
    <p>Although this release bumps Guava's major version number, it makes <strong>no binary-incompatible changes to the <code>guava</code> artifact</strong>.</p>
    <p>One change could cause issues for Widows users, and a few other changes could cause issues for users in more usual situations:</p>
    <ul>
    <li><strong>The new implementations of <code>Files.createTempDir</code> and <code>FileBackedOutputStream</code> <a href="https://redirect.github.com/google/guava/issues/6535">throw an exception under Windows</a>.</strong> This is fixed in <a href="https://togithub.com/google/guava/releases/tag/v32.0.1">32.0.1</a>. Sorry for the trouble.</li>
    <li>This release makes a binary-incompatible change to a <code>@beta</code> API in the <strong>separate artifact</strong> <code>guava-testlib</code>. Specifically, we changed the return type of <code>TestingExecutors.sameThreadScheduledExecutor</code> to <code>ListeningScheduledExecutorService</code>. The old return type was a package-private class, which caused the Kotlin compiler to produce warnings. (dafaa3e435)</li>
    <li>This release <em>adds</em> two methods to the Android flavor of Guava: <code>Invokable.getAnnotatedReturnType()</code> and <code>Parameter.getAnnotatedType()</code>. Those methods do not work under an Android VM; we added them only to help our tests of the Android flavor (since we also run those tests under a JRE). Android VMs tolerate such methods as long as the app does not call them or perform reflection on them, and builds tolerate them because of our new Proguard configurations (discussed below). Thus, we expect no impact to most users. However, we could imagine build problems for users who have set up their own build system for the Android flavor of Guava. Please report any problems so that we can judge how safely we might be able to add other methods to the Android flavor in the future, such as APIs that use Java 8 classes like <code>Stream</code>. (b30e73cfa81ad15c1023c17cfd083255a3df0105)</li>
    </ul>
    <!-- raw HTML omitted -->
    </blockquote>
    <p>... (truncated)</p>
    </details>
    <details>
    <summary>Commits</summary>
    <ul>
    <li>See full diff in <a href="https://togithub.com/google/guava/commits">compare view</a></li>
    </ul>
    </details>
    <br />
    
    
    [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.google.guava:guava&package-manager=maven&previous-version=31.0.1-jre&new-version=32.0.0-jre)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
    
    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-automerge-start)
    [//]: # (dependabot-automerge-end)
    
    ---
    
    <details>
    <summary>Dependabot commands and options</summary>
    <br />
    
    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 merge` will merge this PR after your CI passes on it
    - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
    - `@dependabot cancel merge` will cancel a previously requested merge and block automerging
    - `@dependabot reopen` will reopen this PR if it is closed
    - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    - `@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)
    You can disable automated security fix PRs for this repo from the [Security Alerts page](https://togithub.com/googleapis/sdk-platform-java/network/alerts).
    
    </details>
    dependabot[bot] authored Jun 19, 2023
    Configuration menu
    Copy the full SHA
    9ff8595 View commit details
    Browse the repository at this point in the history

Commits on Jun 20, 2023

  1. feat: GA Gax HttpJson (#1264)

    * feat: Remove @BetaApi for certain httpjson classes
    
    * chore: Fix formatting issues
    
    * chore: Fix formatting issues
    
    * chore: Remove a few more @BetaApi annotations
    
    * chore: Fix format issues
    
    * chore: Revert BetaApi annotation for extraHeaders in gax
    
    * chore: Update BetaApi annotations for subclasses
    
    * chore: Update release please version
    
    * chore: Update all dependencies to new gax-httpjson version
    
    * chore: Update x-version-update tag to be gax-version
    lqiu96 authored Jun 20, 2023
    Configuration menu
    Copy the full SHA
    9f15fea View commit details
    Browse the repository at this point in the history

Commits on Jun 21, 2023

  1. Configuration menu
    Copy the full SHA
    7b89c36 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    4df4450 View commit details
    Browse the repository at this point in the history
  3. chore: Add pagination showcase tests (#1635)

    * chore: Add pagination test for httpjson
    
    * chore: Fix comments
    
    * chore: Add pageToken index as offset
    
    * chore: Clean up pagination tests
    
    * chore: Add grpc test cases
    
    * chore: Fix test comments
    
    * chore: Address PR comments
    
    * chore: Address PR comments
    
    * chore: Remove expand showcase tests
    
    * chore: Use larger pagetoken value
    lqiu96 authored Jun 21, 2023
    Configuration menu
    Copy the full SHA
    56033d5 View commit details
    Browse the repository at this point in the history
  4. build(deps): bump guava to 32.0.1-jre, google-http-client to 1.43.3. (#…

    …1791)
    
    Discrepancy in guava version causing shared dependencies check failures.
    https://github.com/googleapis/sdk-platform-java/actions/runs/5335175946/jobs/9668027541
    manual version bump to be consistent with #1774, #1775. #1776
    
    **Summary of changes in PR:**
    - upgrade guava to 32.0.1-jre
    - upgrade google-http-client to 1.43.3 (with `j2objc-annotation:2.8`)
    - [temp solution] exclude `j2objc-annotations` from `protobuf-java-util` dependencies
    - upgrades `checker-qual` to 3.33.0, `j2objc-annotations` to 2.8 to be consistent
    - add comment to remove temp solution on next `protobuf` upgrade
    zhumin8 authored Jun 21, 2023
    Configuration menu
    Copy the full SHA
    f3da795 View commit details
    Browse the repository at this point in the history

Commits on Jun 22, 2023

  1. build(deps): bump google-auth-library to 1.18.0 (#1793)

    * build(deps): bump google-auth-library to 1.18.0
    
    * fix: update dependencies.properties to auth 1.18.0
    
    ---------
    
    Co-authored-by: Min Zhu <[email protected]>
    burkedavison and zhumin8 authored Jun 22, 2023
    Configuration menu
    Copy the full SHA
    9efb41c View commit details
    Browse the repository at this point in the history
  2. chore(main): release 2.22.0 (#1761)

    Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
    release-please[bot] authored Jun 22, 2023
    Configuration menu
    Copy the full SHA
    324c7d6 View commit details
    Browse the repository at this point in the history
Loading