v0.150.0
Summary
This release contains internal test infrastructure improvements. The TestOSUtils.resource method was updated to stage resources to temporary directories when they cannot be modified in place, enabling unit tests to run unchanged under non-Maven build systems while preserving existing Maven behavior.
Summary generated by brickster.ai. For the full changelog and any code/binary attachments, follow the GitHub link above.
Topics
More from databricks/databricks-sdk-java
The SDK now accepts both JSON numbers and decimal strings when deserializing int64 response fields, fixing deserialization compatibility issues. A new enabledTelemetryFeatures field was added to TelemetryConfig for the Serving API.
This release adds git integration support to Databricks Apps with auto-deploy capabilities and enhanced git repository configuration options. New customUdf field for functions and effectiveServerlessComputeId field for pipeline responses enable better resource tracking and custom function capabilities.
Multiple IAM list methods now require pagination handling (listDirectGroupMembers, listWorkspaceAssignments, and proxy variants), and the bundleDeployments.createOperation() method was removed. The SDK adds LinkedIn Ads and Marketo connector support plus new fields for Genie conversations and serverless compute IDs.
The SDK adds comprehensive IAM v2 API methods to both account and workspace clients for managing groups, users, service principals, and workspace assignments through create, read, list, and delete operations. The `newCluster` field in `JobCluster` is no longer required, making job cluster configuration more flexible.
Job definitions now support trigger configuration and MLflow artifact location for AI runtime tasks. Pipeline connector options and GCP endpoint settings have been expanded with new configuration fields.
The SDK adds support for user token forwarding in apps, custom Docker images in AI runtime jobs, and GPU_XLARGE_8 serving options, plus a secret value retrieval field. ServicePrincipal and User objects now require additional fields (accountSpStatus, displayName for principals; accountUserStatus, fullName, username for users), which is a breaking change for code managing IAM principals or users.