[Release] Release v0.117.0

## Release v0.117.0

### New Features and Improvements
* Detect the `AI_AGENT` environment variable (Vercel `@vercel/detect-agent` convention) as a secondary fallback for the AI agent reported in the user agent, consulted only when the agents.md `AGENT` variable is unset or empty. An unrecognized `AGENT` or `AI_AGENT` value is now passed through as-is (sanitized to the user agent allowlist and capped at 64 characters) instead of being reported as `unknown`. Mirrors [databricks/databricks-sdk-go#1683](databricks/databricks-sdk-go#1683).

* Added `Paginator.newTokenPagination(...)` and `Paginator.newOffsetPagination(...)` factory methods in `com.databricks.sdk.support`, which make the pagination strategy explicit. The `Paginator` constructor is now deprecated in favor of these; it keeps its previous (offset/limit) behavior.

### Bug Fixes

* Fixed `Paginator` silently dropping results when a token-paginated response returned an empty page with a non-empty `next_page_token`. List methods (e.g. `tables().list()`) now keep paging until the page token is absent instead of stopping at the first empty page.

Author: deco-sdk-tagging[bot]

.release_metadata.json

@@ -1,3 +1,3 @@
 {
-    "timestamp": "2026-06-04 09:25:09+0000"
+    "timestamp": "2026-06-08 09:41:57+0000"
 }

CHANGELOG.md

@@ -1,5 +1,17 @@
 # Version changelog
 
+## Release v0.117.0 (2026-06-08)
+
+### New Features and Improvements
+* Detect the `AI_AGENT` environment variable (Vercel `@vercel/detect-agent` convention) as a secondary fallback for the AI agent reported in the user agent, consulted only when the agents.md `AGENT` variable is unset or empty. An unrecognized `AGENT` or `AI_AGENT` value is now passed through as-is (sanitized to the user agent allowlist and capped at 64 characters) instead of being reported as `unknown`. Mirrors [databricks/databricks-sdk-go#1683](https://github.com/databricks/databricks-sdk-go/pull/1683).
+
+* Added `Paginator.newTokenPagination(...)` and `Paginator.newOffsetPagination(...)` factory methods in `com.databricks.sdk.support`, which make the pagination strategy explicit. The `Paginator` constructor is now deprecated in favor of these; it keeps its previous (offset/limit) behavior.
+
+### Bug Fixes
+
+* Fixed `Paginator` silently dropping results when a token-paginated response returned an empty page with a non-empty `next_page_token`. List methods (e.g. `tables().list()`) now keep paging until the page token is absent instead of stopping at the first empty page.
+
+
 ## Release v0.116.0 (2026-06-04)
 
 ### Bug Fixes

NEXT_CHANGELOG.md

@@ -1,18 +1,13 @@
 # NEXT CHANGELOG
 
-## Release v0.117.0
+## Release v0.118.0
 
 ### New Features and Improvements
-* Detect the `AI_AGENT` environment variable (Vercel `@vercel/detect-agent` convention) as a secondary fallback for the AI agent reported in the user agent, consulted only when the agents.md `AGENT` variable is unset or empty. An unrecognized `AGENT` or `AI_AGENT` value is now passed through as-is (sanitized to the user agent allowlist and capped at 64 characters) instead of being reported as `unknown`. Mirrors [databricks/databricks-sdk-go#1683](https://github.com/databricks/databricks-sdk-go/pull/1683).
-
-* Added `Paginator.newTokenPagination(...)` and `Paginator.newOffsetPagination(...)` factory methods in `com.databricks.sdk.support`, which make the pagination strategy explicit. The `Paginator` constructor is now deprecated in favor of these; it keeps its previous (offset/limit) behavior.
 
 ### Breaking Changes
 
 ### Bug Fixes
 
-* Fixed `Paginator` silently dropping results when a token-paginated response returned an empty page with a non-empty `next_page_token`. List methods (e.g. `tables().list()`) now keep paging until the page token is absent instead of stopping at the first empty page.
-
 ### Security Vulnerabilities
 
 ### Documentation

databricks-sdk-java/lockfile.json

@@ -1,7 +1,7 @@
 {
   "artifactId": "databricks-sdk-java",
   "groupId": "com.databricks",
-  "version": "0.116.0",
+  "version": "0.117.0",
   "lockFileVersion": 1,
   "dependencies": [
     {

databricks-sdk-java/pom.xml

@@ -5,7 +5,7 @@
   <parent>
     <groupId>com.databricks</groupId>
     <artifactId>databricks-sdk-parent</artifactId>
-    <version>0.116.0</version>
+    <version>0.117.0</version>
   </parent>
   <artifactId>databricks-sdk-java</artifactId>
   <name>Databricks SDK for Java</name>

databricks-sdk-java/src/main/java/com/databricks/sdk/core/UserAgent.java

@@ -36,7 +36,7 @@ public String getValue() {
   // TODO: check if reading from
   // /META-INF/maven/com.databricks/databrics-sdk-java/pom.properties
   // or getClass().getPackage().getImplementationVersion() is enough.
-  private static final String version = "0.116.0";
+  private static final String version = "0.117.0";
 
   public static void withProduct(String product, String productVersion) {
     UserAgent.product = product;

examples/docs/pom.xml

@@ -24,7 +24,7 @@
     <dependency>
       <groupId>com.databricks</groupId>
       <artifactId>databricks-sdk-java</artifactId>
-      <version>0.116.0</version>
+      <version>0.117.0</version>
     </dependency>
   </dependencies>
 </project>

examples/spring-boot-oauth-u2m-demo/pom.xml

@@ -40,7 +40,7 @@
     <dependency>
       <groupId>com.databricks</groupId>
       <artifactId>databricks-sdk-java</artifactId>
-      <version>0.116.0</version>
+      <version>0.117.0</version>
     </dependency>
   </dependencies>
 </project>

lockfile.json

@@ -1,7 +1,7 @@
 {
   "artifactId": "databricks-sdk-parent",
   "groupId": "com.databricks",
-  "version": "0.116.0",
+  "version": "0.117.0",
   "lockFileVersion": 1,
   "dependencies": [],
   "mavenPlugins": [],

pom.xml

@@ -4,7 +4,7 @@
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.databricks</groupId>
   <artifactId>databricks-sdk-parent</artifactId>
-  <version>0.116.0</version>
+  <version>0.117.0</version>
   <packaging>pom</packaging>
   <name>Databricks SDK for Java</name>
   <description>The Databricks SDK for Java includes functionality to accelerate development with Java for