fix(deps): update all non-major gomod dependencies #547
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.12.0-rc.4
->v1.13.0
v1.9.1
->v1.10.1
v5.0.10
->v5.0.12
v10.16.0
->v10.19.0
v1.5.3
->v1.5.4
v5.5.3
->v5.5.5
v1.2.17
->v1.8.1
v9.1.0
->v9.5.1
v0.46.1
->v0.49.0
v1.23.1
->v1.24.0
v1.23.1
->v1.24.0
v1.23.1
->v1.24.0
v1.23.1
->v1.24.0
v1.23.1
->v1.24.0
v1.23.1
->v1.24.0
v0.21.0
->v0.22.0
v0.15.0
->v0.18.0
v1.61.1
->v1.62.1
v1.61.0
->v1.62.1
v1.32.0
->v1.33.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
dapr/dapr (github.com/dapr/dapr)
v1.13.0
: Dapr Runtime v1.13.0Compare Source
Dapr 1.13
We're happy to announce the release of Dapr 1.13!
We would like to extend our thanks to all the new and existing contributors who helped make this release happen.
If you're new to Dapr, visit the getting started page and familiarize yourself with Dapr.
Docs have been updated with all the new features and changes of this release.
To get started with new capabilities introduced in this release, go to the Concepts and the Developing applications.
See this section on upgrading Dapr to version 1.13.
Highlights
These are the v1.13 release highlights:
Component hot reloading (preview)
Component "Hot Reloading" is a new preview feature that, when enabled, allows component updates to be picked up automatically, without the need for restarting the Dapr process.
The component spec is reconciled and takes effect when running in both Kubernetes and Self-Hosted modes.
Go and JavaScript/TypeScript SDK support for workflow
You can now use Go and JavaScript/TypeScript to write fault-tolerant, workflow-based apps with durable execution.
See the Go SDK for more details and try the Quickstart or the examples.
See the Javascript SDK for more details and try the Quickstart or the examples
Actor reminders performance improvement
You can now opt-in to make actor reminders data use protobuf serialization instead of JSON, which increases throughput, reduces latency, and improves stability when multiple Dapr instances are operating on the same reminders.
With this feature enabled, we have observed improvements as high as 40% in Actor Reminders and Workflow benchmarks.
This serialization method will become default in v1.14.
To enable protobuf serialization for actor reminders, set the following Helm argument on Kubernetes:
dapr_placement.maxActorApiLevel=20
.On self-hosted mode, run daprd with the flag:
--max-api-level=20
Low metrics cardinality for HTTP server
Dapr now includes an optional setting to enable low cardinality for metrics emitted by the HTTP server, which will be enabled by default in Dapr 1.14.
Currently, the Dapr HTTP server emits metrics for each request path, which has been observed to cause significant memory usage and have other negative performance impact.
When low-cardinality metrics are enabled, the HTTP Dapr server behaves more like the gRPC server and groups requests for each Dapr API together, possibly reducing memory consumption significantly.
See additional info here.
Graceful shutdown
Dapr now accepts a
dapr.io/block-shutdown-duration
annotation or--dapr-block-shutdown-duration
CLI flag which delays the full shutdown procedure for this duration or until the app reports as unhealthy- whichever is sooner.During this period, all Subscriptions and input bindings will be closed.
This is useful for applications that need to use the Dapr APIs as part of their own shutdown procedure.
See additional info here.
Standardized error codes
The Dapr PubSub and State APIs now have the appropriate and standardized error codes returned to applications including enriched error details based on gRPC's richer error model.
The remaining APIs are a work in progress, and community contributions towards this effort are greatly appreciated and very impactful.
See additional info on the error codes here.
Check the docs for each SDK for per-SDK error code parsing and handling.
See an example of the Go SDK error parsing and handling here.
Rust SDK support for actors (alpha)
You can now use Rust to run Dapr Actors, a programming model for highly scalable stateful applications.
See the Rust SDK for more details
Components
Local name resolver based on SQLite
You can now use a SQLite based name resolver for service invocation in self-hosted mode.
This is useful for dealing with corporate firewalls and VPNs that filter mDNS.
See additional info here.
PostgreSQL state store v2
PostgreSQL has a new v2 implementation which contains improvements to performance and reliability.
New applications are encouraged to use v2.
The v1 implementation remains supported and is not deprecated.
There is no migration path from v1 to v2.
See additional info here.
Azure Blob Storage state store v2
Azure Blob Storage has a new v2 implementation, which is recommended for all new projects as it fixes a backwards-incompatible bug with key prefixes.
The v1 implementation remains supported and is not deprecated.
There is no migration path from v1 to v2.
See additional info here.
Acknowledgements
Thanks to everyone who made this release possible!
@a-elsheikh, @addjuarez, @AishwaryaBalyaya01, @alfred-mikhael, @amimimor, @andreas-eriksson, @andrew-hillier, @arthbalete, @artursouza, @ASHIQUEMD, @avo-sepp, @baransonmez, @berndverst, @bkc, @bmelbourne, @bruth, @burhan, @cgillum, @chaitanyab2311, @cicoyle, @ckcd, @cscetbon, @danielgerlag, @dasanind, @DeepanshuA, @ejba, @elena-kolevska, @emctl, @eunicecompra, @famarting, @farshaddavoudi, @fazledyn-or, @filintod, @frankbuckley, @frodera, @fvandillen, @fyzact, @georgestevens99, @Gonzoe79, @greenie-msft, @gspadotto, @hauju, @henrikkarstrom, @heunghingwan, @hhunter-ms, @ItalyPaleAle, @jamesmcroft, @jancespivo, @jellis18, @jerinthomas1404, @jhberge, @jigargandhi, @jjcollinge, @jorimvanhove, @JoshVanL, @kaibocai, @KarstenWintermann, @KrylixZA, @litan1106, @lrascao, @lucus-sun, @luigirende, @macel94, @marcduiker, @martbln, @mathieu-benoit, @mikeee, @MregXN, @msfussell, @mukundansundar, @nitroin, @olitomlinson, @paianish62, @passuied, @paulyuk, @philliphoff, @pngan, @prashantrewar, @prateek041, @pravinpushkar, @qustavo, @rabollin, @robertojrojas, @RyanLettieri, @sadath-12, @salaboy, @shivamkm07, @shubham1172, @sicoyle, @siebenluke, @skyao, @srilasya02, @srparupu, @stuartleeks, @Taction, @thapasusheel, @tlund101, @tmacam, @toneill818, @TWEESTY, @twinguy, @vermillionsword, @Viktorsubota, @willvelida, @WhitWaldo, @XavierGeerinck, @xiangpingjiang, @yaron2, @yash-nisar, @ytimocin
New in this release
Dapr Runtime
ghcr.io
in Helm chart 6413 7176priorityClass
in Helm charts 7103 7395dapr_sidecar_injector.enableK8sDownwardAPIs
to improve detection of pod IP in certain Kubernetes environments 7511--dapr-block-shutdown-duration
to daprd 7268 4313grpc_server_status
label missing for gRPC server latency metric 7045 7255deploymentAnnotations
produces invalid Helm chart 7194RenameReminder
methods 6711 6945AppChannelAllowInsecureTLS
feature flag, and require TLS-enabled app channel to use TLS 1.2+ 7292 7149content-length
metadata in pubsub subscription. 7413 7421Components
Dapr 1.13 introduces 3 new components:
This new version of the PostgreSQL state store can offer up to 10% improved performance in some scenarios.
This version supports all stable capabilities, including Actor State Store; support for the Alpha Query API.
Note that the v1 of the component continues to be supported and there are currently no plans to deprecate it.
This version addresses a fundamental breaking change in the handling of the state key prefix.
Note that the v1 of the component continues to be supported and there are currently no plans to deprecate it.
This component is particularly useful in local development or in single-node deployments, as an alternative to the default mDNS name resolver.
Additionally, one component has been removed:
Other improvements and fixes to components:
ttl
is now an alias forttlInSeconds
and accepts a Go duration format in addition to seconds as whole numbers 3122ttl
is now an alias forttlInSeconds
and accepts a Go duration format in addition to seconds as whole numbers 3122disableEntityManagement
metadata option to work with minimal Microsoft Entra ID permissions 3213EnableHostVerification
3230azureAuthMethods
component metadata 3183 3217Dapr CLI
~/.dapr
given 777 permisions. 1317.NET SDK
Go SDK
Java SDK
Python SDK
wait
method is now deprecated and will be removed in a future release. The automatic outbound health check covers this use case.Python Workflow Alpha SDK (
dapr-ext-workflow
)JavaScript SDK
Rust SDK
Quickstarts
Dapr 1.13 Quickstarts include these major updates:
Other improvements include:
process.env.STATE_STORE_NAME
958https://github.com/dapr/quickstarts/pull/976/976)
Upgrading to Dapr 1.13
To upgrade to this release of Dapr, follow the steps here to ensure a smooth upgrade.
You know, the one where you don't get red errors on the terminal.. we all hate that, right?
Local Machine / Self-hosted
Uninstall Dapr using the CLI you currently have installed.
Note that this will remove the default $HOME/.dapr directory, binaries and all containers dapr_redis, dapr_placement and dapr_zipkin.
Linux users need to run sudo if docker command needs sudo:
For RC releases like this, download the latest and greatest release from here and put the
dapr
binary in your PATH.Once you have installed the CLI, run:
Wait for the update to finish, ensure you are using the latest version of Dapr(1.13) with:
Kubernetes
Upgrading from previous version
You can perform zero-downtime upgrades using both Helm 3 and the Dapr CLI.
Upgrade using the CLI
Download the latest RC release from here and put the
dapr
binary in your PATH.To upgrade Dapr, run:
To upgrade with high availability mode:
Wait until the operation is finished and check your status with
dapr status -k
.All done!
Note: Make sure your deployments are restarted to pick the latest version of the Dapr sidecar
Upgrade using Helm
To upgrade Dapr using Helm, run:
Wait until the operation is finished and check your status with
dapr status -k
.All done!
Note: Make sure your deployments are restarted to pick the latest version of the Dapr sidecar
Starting a fresh install on a cluster
Please see how to deploy Dapr on a Kubernetes cluster for a complete guide to installing Dapr on Kubernetes
You can use Helm 3 to install Dapr:
Alternatively, you can use the latest version of CLI:
Post installation
Verify the control plane pods are running and are healthy:
After Dapr 1.13 has been installed, perform a rolling restart for your deployments to pick u
Configuration
📅 Schedule: Branch creation - "* 18-21 * * 5" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.