fix(deps): update all non-major gomod dependencies #783
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
requested review from
FoseFx and
PaulKalho
and removed request for
a team
renovate
bot
force-pushed
the
renovate/all-non-major-gomod-dependencies
branch
4 times, most recently
from
bcca5fe
to
f43e9ef
Compare
ℹ Artifact update noticeFile name: libs/common/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: services/ory-svc/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: libs/telemetry/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: libs/hwdb/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: libs/hwutil/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: libs/hwlocale/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: services/user-svc/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: services/tasks-svc/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: services/task-svc/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: services/property-svc/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/all-non-major-gomod-dependencies
branch
7 times, most recently
from
5b81bb6
to
de7eadb
Compare
renovate
bot
force-pushed
the
renovate/all-non-major-gomod-dependencies
branch
4 times, most recently
from
78c2567
to
6537386
Compare
renovate
bot
force-pushed
the
renovate/all-non-major-gomod-dependencies
branch
2 times, most recently
from
759f787
to
43d29ce
Compare
renovate
bot
force-pushed
the
renovate/all-non-major-gomod-dependencies
branch
from
43d29ce
to
461fec5
Compare
renovate
bot
force-pushed
the
renovate/all-non-major-gomod-dependencies
branch
6 times, most recently
from
29b9947
to
a75f8a8
Compare
renovate
bot
force-pushed
the
renovate/all-non-major-gomod-dependencies
branch
3 times, most recently
from
e7eca91
to
7dd51e8
Compare
renovate
bot
force-pushed
the
renovate/all-non-major-gomod-dependencies
branch
from
7dd51e8
to
6bd08bb
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
FoseFx
approved these changes
Aug 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.13.4->v1.14.0v5.0.12->v5.1.0v1.11.7->v1.14.3v9.5.3->v9.6.1v0.52.0->v0.53.0v1.27.0->v1.28.0v1.27.0->v1.28.0v1.27.0->v1.28.0v1.27.0->v1.28.0v1.27.0->v1.28.0v1.27.0->v1.28.0v0.26.0->v0.28.0v0.21.0->v0.22.0v0.16.0->v0.17.0v1.64.0->v1.65.0Release Notes
dapr/dapr (github.com/dapr/dapr)
v1.14.0: Dapr Runtime v1.14.0Compare Source
Dapr 1.14
We're excited to announce the release of Dapr 1.14!
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.14.
Highlights
These are the new feature highlights for the v1.14 release:
Jobs API and Scheduler service (preview)
Many applications require job scheduling, or the need to take an action in the future. The new jobs API is an orchestrator for scheduling these future jobs, either at a specific time or for a specific interval. For example job scheduling is useful in scenarios such as automated database backups, regular Data Processing and ETL, email notifications, maintenance tasks and system updates and batch processing to name a few.
The Dapr’s Jobs API ensures the tasks represented in these types of scenarios are performed consistently and reliably, improving efficiency and reducing the risk of errors. Think of this as a scalable version of the popular Dapr Cron Binding, now as a first class API available via the Dapr SDKs.
You can read more in the Jobs API overview documentation, or dive into a Quickstart Go code example. Support for Jobs is also in the alpha Rust-SDK!
Scheduler service (preview)
The Scheduler service is a new control plane service used to schedule jobs, running in self-hosted mode or on Kubernetes. It is installed by when using Helm or the Dapr CLI and is the service responsible for managing the scheduled jobs.
Increased throughput and scalability for actors and workflows (preview)
The new Scheduler service can optionally be used as the backend for actor reminders and enables increased throughput and lower latency for both actors and workflows. To use the scheduler service for actors and workflows, simply enable it in a Dapr Configuration resource like this:
Important note: Existing reminder data is not be compatible with the scheduler service. The scheduler service should be used only for new actor and workflow reminders
Streaming subscriptions (preview)
Streaming subscriptions are a new type of subscription written in code. Streaming subscriptions are dynamic, meaning they allow for adding or removing subscriptions at runtime. They do not require a subscription HTTP endpoint in your application (which is required by the current programmatic and declarative subscriptions), making them easy to configure in code. Streaming subscriptions also do not require an app to be configured with the sidecar to receive messages. These are an incredibly easy way to configure topic subscriptions for your app. In this release streaming subscriptions are available in the Go SDK.
Actor multi-tenancy with namespacing
Namespacing in Dapr provides isolation, and thus multi-tenancy. With actor namespacing, the same actor type can be deployed into different namespaces. You can then call instances of these actors within the same namespace. Each namespaced actor deployment must use its own separate state store, especially if the same actor type is deployed into different namespaces.
HTTP metrics filtering with path matching
When invoking Dapr using HTTP, metrics are created for each requested method by default. For example metrics include error rates, latency and throughput numbers. This can result in a high number of metrics being reported, known as high cardinality, which can impact memory usage and CPU for your application.
HTTP metric path matching allows you to manage and control the cardinality, or the amount, of HTTP metrics in Dapr. This is an aggregation of metrics, so rather than having a metric for each event, you can reduce the number of metrics events and report an overall number.
Outbox message projections (stable)
The transactional outbox feature allows you to commit state and then send a message in a single transaction and can be used with a broad combination of pub/sub brokers and databases. The transactional outbox is now stable in v1.14 release.
Now in this release, when using the outbox pattern, you can send a different payload to the pub/sub broker than the one saved in the database. These are called outbox message projections, and can be shaped in any way you need.
Service invocation for non-Dapr endpoints (stable)
The ability to invoke non-Dapr endpoints using the Dapr Service invocation APIis now stable.
Dapr Shared (new preview repo in Dapr org)
Although not part of the Dapr runtime v1.14 release, Dapr Shared provides alternative deployment choices for Dapr.
Dapr, by default, is injected as a sidecar to enable the Dapr APIs for your applications for the best availability and reliability. Dapr Shared enables two alternative deployment strategies to create Dapr applications using a Kubernetes Daemonset for a per-node deployment or a Deployment for a per-cluster deployment.
For example, Dapr Shared can be used to reduce resource usage in a cluster or to make a simpler testing deployment environment.
Python SDK updates
Acknowledgements
Thanks to everyone who made this release possible!
@aharonYK, @akshaya-a, @amardeep2006, @andrejpk, @andriisoldatenko, @AnnuCode, @antoniomaria, @agoktugaydin, @alundiak, @andrew-hillier, @antontroshin, @artur-ciocanu, @artursouza, @avoidalone, @berndverst, @bibryam, @bhagya05, @bkc, @bondz, @c-thiel, @cgillum, @cicoyle, @ckcd, @cmendible, @contributor, @daixiang0, @DeepanshuA, @denisbchrsk, @DropSnorz, @ductnn, @dwhiteddsoft, @ecabrerar, @Eileen-Yu, @elena-kolevska, @erwinkramer, @evacchi, @evhen14, @fabistb, @famarting, @james-bartlett, @filintod, @guspan-tanadi, @gralin, @hhunter-ms, @ibandhiya, @imneov, @ItalyPaleAle, @jake-engelberg, @jcchavezs, @jjcollinge, @jmprusi, @joebowbeer, @JoshVanL, @Jossec101, @kaibocai, @KrylixZA, @KentHsu, @kindknow, @ksachdeva, @laurentkempe, @m3nax, @mahparaashley, @marcoscale98, @manojks1999, @MattCosturos, @MichaelHindley, @mikeee, @MO2k4, @mohitpalsingh, @moonorange, @msfussell, @mukundansundar, @nadavv169, @nathandl86, @nelson-parente, @nenikola, @newbe36524, @nikitasarawgi, @olitomlinson, @passuied, @paulyuk, @pdebruin, @philliphoff, @pravinpushkar, @RafaelJCamara, @robertojrojas, @rochabr, @ruokun-niu, @Rutam21, @RyanLettieri, @sadath-12, @salaboy, @svdspradeep, @SantoDE, @shivam-51, @shivamkm07, @shubham1172, @Shubhdeep02, @sicoyle, @Taction, @thewilli, @thompson-tomo, @ThomasVitale, @tmacam, @toneill818, @TomasEkeli, @tlund101, @umerkle, @waltercoan, @wardbeyens, @WhitWaldo, @willtsai, @XavierGeerinck, @yaron2, @zedgell
New in this release
Dapr Runtime
Dapr CLI
daprCLI 1032dapr status -kcommand does not show the scheduler service. 1433Components
autodeleteonidlesecminimum of 300 3340pubsub.solace.amqp3451Dashboard
.NET SDK
Go SDK
Java SDK
Python SDK
dapr-ext-grpc722Rust SDK
JavaScript SDK
Quickstarts
Upgrading to Dapr 1.14
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
daprbinary 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.14) with:
Kubernetes
Upgrading from previous version
You can perform zero-downtime upgrades using both Helm 3 and the Dapr CLI.
Upgrade using the CLI
We've got some handy install scripts available: https://docs.dapr.io/getting-started/install-dapr-cli/ making sure to specify
1.14.0as the CLI version.Alternatively - download the latest release from here and put the
daprbinary 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.14 has been installed, perform a rolling restart for your deployments to pick up the new version of the sidecar.
This can be done with:
Breaking changes
Java SDK
Actor placement (cross-namespace actor invocation)
Actors are now namespaced, meaning that cross-namespace actor invocation is no longer supported. You must ensure that all actor invocations occur within the same namespace.
Deprecation Notices
None.
v1.13.5: Dapr Runtime v1.13.5Compare Source
Dapr 1.13.5
Updated dependencies
Updated multiple dependencies to address reported vulnerabilities.
Currently, none of the vulnerabilities in the updated dependencies are known to be exploitable in Dapr.
Update to accomodate users that need to comply with automated vulnerability scanning tools.
go-chi/chi (github.com/go-chi/chi/v5)
v5.1.0Compare Source
What's Changed
Discard()method to themiddleware.WrapResponseWriterinterface. This is technically an API breaking change. However after some discussion at https://github.com/go-chi/chi/pull/926#discussion_r1658333481, we decided to move forward, and release as minor version, as we don't expect anyone to rely on this interface / implement it externally.New Contributors
Full Changelog: go-chi/chi@v5.0.14...v5.1.0
v5.0.14Compare Source
v5.0.13Compare Source
What's Changed
New Contributors
Full Changelog: go-chi/chi@v5.0.12...v5.0.13
ory/client-go (github.com/ory/client-go)
v1.14.3Compare Source
v1.14.2Compare Source
v1.14.1Compare Source
v1.14.0Compare Source
v1.13.10Compare Source
v1.13.6Compare Source
v1.13.4Compare Source
v1.13.3Compare Source
v1.13.2Compare Source
v1.13.1Compare Source
v1.13.0Compare Source
v1.12.2Compare Source
v1.12.1Compare Source
v1.12.0Compare Source
v1.11.12Compare Source
v1.11.11Compare Source
v1.11.10Compare Source
redis/go-redis (github.com/redis/go-redis/v9)
v9.6.1: 9.6.1Compare Source
Changes
9.6
This release contains all new features from version 9.6.
🚀 New Features
9.6.1
In addition minor changes were performed to retract version 9.5.3 and 9.5.4 that were released accidentally.
🧰 Maintenance
🎁 Package Distribution
Contributors
We'd like to thank all the contributors who worked on this release!
@LINKIWI, @b1ron, @gerzse, @haines, @immersedin, @naiqianz, @ofekshenawa, @srikar-jilugu, @tzongw, @vladvildanov, @vmihailenco and @monkey92t
v9.6.0: 9.6.0Compare Source
Changes
🚀 New Features
🛠️ Improvements
This release includes support for Redis Community Edition (CE) 7.4.0, ensuring compatibility with the latest features and improvements introduced in Redis CE 7.4.0.
🧰 Maintenance
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 was generated by Mend Renovate. View the repository job log.