GeezerVison

This upgrade from version 1.8.0 to 1.17.6 of the Dapr Java SDK spans numerous minor releases and includes significant feature stabilizations and at least one notable breaking change that requires developer action.

Key Changes & Risks:

• HIGH RISK - Service Invocation Content-Type: As of Dapr runtime v1.9.0, application/json is no longer the default Content-Type header for service invocation calls. If your application relies on this default, you must explicitly set the Content-Type header in your calls to prevent runtime failures.

• MEDIUM RISK - Environment: Java Version: While Dapr SDK v1.17.x is the last series to support JDK 11, the subsequent Dapr v1.18 release requires Java 17. Teams should verify their current JDK environment and plan for a required upgrade to Java 17 before any future Dapr updates.

• API Stabilization - Bulk Pub/Sub: The Bulk Pub/Sub API, introduced as an alpha feature, was stabilized in v1.17. While backward compatibility is maintained for subscribers, client code should be updated to use the new stable publishEvents methods to align with the production-ready API and avoid future deprecation warnings.

• API Stabilization - Workflows: The Workflow API was introduced and stabilized (v1.15) within this version range. Older alpha versions of the API were deprecated. Applications using workflows should ensure they are using the stable client APIs.

Recommendation:

1. Mandatory: Review all service invocation calls and explicitly add the Content-Type header where it was previously assumed to be application/json.
2. Verify: Confirm your production environment runs on at least JDK 11 and create a plan to migrate to JDK 17 for future Dapr compatibility.
3. Review: If using Bulk Pub/Sub or Workflows, audit your code to ensure you are using the stable, non-alpha versions of the SDK methods.

Source: Dapr Breaking Changes Documentation, Dapr v1.17 Release Highlights

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}