Dapr v1.4 is now available
We are excited to announce the release of Dapr v1.4!
This is the fourth minor version update since the announcement of Dapr v1.0.
If you’re new to Dapr, familiarize yourself by visiting the getting started page.
- Added an HTTP proxy feature for service to service calls similar to gRPC proxy #3546. Now it’s easier to use Dapr features with existing HTTP client code. Simply add a line of metadata with your appid, and call the service (without using Dapr’s special URLs or requiring Dapr SDK for service invoke). For more info, see the docs.
- Enabled pub/sub subscribers to perform message routing and filtering based on expressions applied to CloudEvents fields (preview feature). #2582. For more info, see the docs.
- Added automatic encryption of data with support for key rotation (preview feature) #1090. Enable automatic data-at-rest encryption of your state with support for bringing-your-own-key and key rotation. Supports all Dapr state stores. For more info, see the docs.
- Added the option to specify an HTTP endpoint route for input bindings #3520. For more info, see the docs.
- In memory Pub/Sub broker
- NATS JetStream Pub/Sub broker
- Alibaba Cloud Tablestore binding
- AWS SES binding
See a detailed description of changes, fixes and new features in the Dapr v1.4 release notes.
This release contains a few breaking changes.
Dapr supports two (2) prior versions from the current release.
This means that there is a rolling window that moves forward for supported releases and it is your operational responsibility to remain up to date with these supported versions. If you have an older version of Dapr you may have to do intermediate upgrades to get to a supported version.
Since this release marks v1.4.0, the two prior supported versions are v1.2.0 and v1.3.0.
Please visit the Dapr Documentation for more information on supported releases.
Installing and upgrading to Dapr v1.4
ImportantIf you are running a production cluster and cannot handle some downtime there are special steps that required to upgrade from 1.3.0 to 1.4.0 to ensure no downtime. See Production upgrade from 1.3.0 to 1.4.0 for detailed steps.
To get started with Dapr v1.4, please see the getting started guide.
For a complete guide to installing Dapr on Kubernetes, please see how to deploy Dapr on a Kubernetes cluster.
To upgrade to this release of Dapr, follow the applicable links below:
Thank you to everyone who made this release possible!
@1046102779, @AaronCrawfis, @CodeMonkeyLeet, @Fabian-Schmidt, @ItalyPaleAle, @LLKennedy, @TomCools, @UmutComlekci, @amimimor, @artursouza, @beiwei30, @berndverst, @blackstorm, @cshi0, @daixiang0, @dmitsh, @fjvela, @greenie-msft, @halspang, @howlowck, @jigargandhi, @kevinten10, @l0ll098, @li1234yun, @luckyxiaoqiang, @marcmaranon, @marviniter, @matthewgaim, @msfussell, @mthmulders, @mukundansundar, @omidb, @orizohar, @paulyuk, @pkedy, @ravi-k4, @riezebosch, @tanvigour, @theonefx, @variadico, @vikborisov, @wcs1only, @weibubli, @willtsai, @yaron2, @yufan022, @jerrylisl, @variadico
We hope you try out this new release and raise issues on GitHub as well as reach out to us to ask questions on Discord or via Twitter. We also encourage you to attend our recurring Dapr community calls to see demos and discuss new feature proposals with the rest of the Dapr community!