Bump Consul, Ocelot and Ocelot.Provider.Consul#1663
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
Bump Consul, Ocelot and Ocelot.Provider.Consul#1663dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps Consul from 1.7.14.7 to 1.7.14.9 Bumps Ocelot from 24.0.0 to 24.1.0 Bumps Ocelot.Provider.Consul from 24.0.0 to 24.1.0 --- updated-dependencies: - dependency-name: Consul dependency-version: 1.7.14.9 dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: Ocelot dependency-version: 24.1.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: Ocelot.Provider.Consul dependency-version: 24.1.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
.NET
|
This file contains hidden or 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
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.
Updated Consul from 1.7.14.7 to 1.7.14.9.
Release notes
Sourced from Consul's releases.
1.7.14.9
What's Changed
Full Changelog: G-Research/consuldotnet@v1.7.14.8...v1.7.14.9
1.7.14.8
What's Changed
New Contributors
Full Changelog: G-Research/consuldotnet@v1.7.14.7...v1.7.14.8
Commits viewable in compare view.
Updated Ocelot from 24.0.0 to 24.1.0.
Release notes
Sourced from Ocelot's releases.
24.1.0
Summer-Autumn 2025 (version 24.1) aka Globality release
ℹ️ About
In this minor release, the Ocelot team put the spotlight on the Configuration feature as part of their semi-annual 2025 effort, with a particular focus on the Global Configuration Schema. This release enhances support for global configurations across both routing modes: the classic static Routing and the service discovery-based Dynamic Routing.
The updated documentation highlights the deprecation of certain options through multiple notes and warnings. This deprecation process will be completed in the upcoming .NET 10 release. With the
[Obsolete]attributes in place, C# developers will notice several warnings in the build logs during compilation.On top of that, this release brings a great enhancement to the Kubernetes provider, also known as the Ocelot.Provider.Kubernetes package.
🆕 What's New?
Configuration: The "Dynamic routing global configuration" feature has been redesigned by @raman-m and contributors.
This update brings changes to the Dynamic Route Schema and Global Configuration Schema, while the Route Schema stays the same apart from deprecation updates. All work was coordinated under issue #585, which addressed the challenges of configuring Ocelot's most popular features globally before version 24.1, when dynamic routing gained global configuration partial support, but static routing mostly lacked it. A key outcome of #585 is the ability to override global configuration options within the
DynamicRoutescollection. This ongoing issue will continue to require attention, as adapting static route global configurations for dynamic routing is complex and, in some cases, impossible. This will be a challenge for future Ocelot releases and the community.Kubernetes: The "Kubernetes provider based on watch requests" feature by @kick2nick in PR #2174. ⭐
The Ocelot.Provider.Kubernetes package now features a new WatchKube provider for Kubernetes service discovery. This provider is a great fit for high-load environments where the older
KubeandPollKubeproviders struggle to handle heavy traffic, often leading to increased log errors, HTTP 500 issues, and potential Ocelot instance failures.WatchKubeis the next step in the evolution of these providers, leveraging the reactive capabilities of the KubeClient API. For guidance on choosing the right provider for your Kubernetes setup, check out the "Comparing providers" section in the documentation.Configuration: The "Routing default timeout" feature by @hogwartsdeveloper in PR #2073.
In the past, the
Timeoutsetting in the Route Schema didn't actually stop requests, defaulting instead to a fixed 90 seconds. Custom timeouts were handled using the Quality of Service Timeout strategy, and this only applied if Polly and the Ocelot.Provider.Polly package were used. Now, theTimeoutoption (in seconds) can be set at the route, global, and QoS levels. The Global Configuration Schema and Dynamic Route Schema also include the newTimeoutsetting, making it possible to configure default timeouts for dynamic routing as well.Quality of Service: The "FailureRatio and SamplingDuration parameters of Polly V8 circuit-breaker" feature by @RaynaldM in PR #2081.
Starting with version 24.1, two new parameters in QoSOptions,
FailureRatioandSamplingDuration, let you fine-tune the behavior of the Circuit Breaker strategy. Both can be configured globally, even with dynamic routing.Please note that
DurationOfBreak,ExceptionsAllowedBeforeBreaking, andTimeoutValueare now deprecated in 24.1, so check the QoSOptions Schema documentation for details.🆙 What's Updated?
Configuration: Several File-model options have been deprecated by @raman-m.
The updated docs now highlight these deprecated options with multiple notes and warnings. The v24.1 deprecation process will wrap up in the upcoming .NET 10 release. Due to the
Obsoleteattributes, C# developers will notice several build warnings during compilation.... (truncated)
24.0.1
Ocelot.Administration.IdentityServer4 version 24.0.1
❗ Breaking Changes
The Ocelot.Administration extension package has been renamed to Ocelot.Administration.IdentityServer4 ❗
Feature: Administration
All IdentityServer4-related vulnerabilities (issue #2218) were addressed. The Ocelot.Administration source code has been moved out of the Ocelot repository (pull request #2274) and transferred to the Ocelot.Administration.IdentityServer4 repository.
Currently, the Administration feature is solely based on the IdentityServer4 package, whose repository was archived by its owner on July 31, 2024. In this release, the Ocelot team deprecated the Ocelot.Administration.IdentityServer4 extension package after the current Ocelot v24.0 release; however, the repository is/will not be archived, allowing for potential patches in the future.
Commits viewable in compare view.
Updated Ocelot.Provider.Consul from 24.0.0 to 24.1.0.
Release notes
Sourced from Ocelot.Provider.Consul's releases.
24.1.0
Summer-Autumn 2025 (version 24.1) aka Globality release
ℹ️ About
In this minor release, the Ocelot team put the spotlight on the Configuration feature as part of their semi-annual 2025 effort, with a particular focus on the Global Configuration Schema. This release enhances support for global configurations across both routing modes: the classic static Routing and the service discovery-based Dynamic Routing.
The updated documentation highlights the deprecation of certain options through multiple notes and warnings. This deprecation process will be completed in the upcoming .NET 10 release. With the
[Obsolete]attributes in place, C# developers will notice several warnings in the build logs during compilation.On top of that, this release brings a great enhancement to the Kubernetes provider, also known as the Ocelot.Provider.Kubernetes package.
🆕 What's New?
Configuration: The "Dynamic routing global configuration" feature has been redesigned by @raman-m and contributors.
This update brings changes to the Dynamic Route Schema and Global Configuration Schema, while the Route Schema stays the same apart from deprecation updates. All work was coordinated under issue #585, which addressed the challenges of configuring Ocelot's most popular features globally before version 24.1, when dynamic routing gained global configuration partial support, but static routing mostly lacked it. A key outcome of #585 is the ability to override global configuration options within the
DynamicRoutescollection. This ongoing issue will continue to require attention, as adapting static route global configurations for dynamic routing is complex and, in some cases, impossible. This will be a challenge for future Ocelot releases and the community.Kubernetes: The "Kubernetes provider based on watch requests" feature by @kick2nick in PR #2174. ⭐
The Ocelot.Provider.Kubernetes package now features a new WatchKube provider for Kubernetes service discovery. This provider is a great fit for high-load environments where the older
KubeandPollKubeproviders struggle to handle heavy traffic, often leading to increased log errors, HTTP 500 issues, and potential Ocelot instance failures.WatchKubeis the next step in the evolution of these providers, leveraging the reactive capabilities of the KubeClient API. For guidance on choosing the right provider for your Kubernetes setup, check out the "Comparing providers" section in the documentation.Configuration: The "Routing default timeout" feature by @hogwartsdeveloper in PR #2073.
In the past, the
Timeoutsetting in the Route Schema didn't actually stop requests, defaulting instead to a fixed 90 seconds. Custom timeouts were handled using the Quality of Service Timeout strategy, and this only applied if Polly and the Ocelot.Provider.Polly package were used. Now, theTimeoutoption (in seconds) can be set at the route, global, and QoS levels. The Global Configuration Schema and Dynamic Route Schema also include the newTimeoutsetting, making it possible to configure default timeouts for dynamic routing as well.Quality of Service: The "FailureRatio and SamplingDuration parameters of Polly V8 circuit-breaker" feature by @RaynaldM in PR #2081.
Starting with version 24.1, two new parameters in QoSOptions,
FailureRatioandSamplingDuration, let you fine-tune the behavior of the Circuit Breaker strategy. Both can be configured globally, even with dynamic routing.Please note that
DurationOfBreak,ExceptionsAllowedBeforeBreaking, andTimeoutValueare now deprecated in 24.1, so check the QoSOptions Schema documentation for details.🆙 What's Updated?
Configuration: Several File-model options have been deprecated by @raman-m.
The updated docs now highlight these deprecated options with multiple notes and warnings. The v24.1 deprecation process will wrap up in the upcoming .NET 10 release. Due to the
Obsoleteattributes, C# developers will notice several build warnings during compilation.... (truncated)
24.0.1
Ocelot.Administration.IdentityServer4 version 24.0.1
❗ Breaking Changes
The Ocelot.Administration extension package has been renamed to Ocelot.Administration.IdentityServer4 ❗
Feature: Administration
All IdentityServer4-related vulnerabilities (issue #2218) were addressed. The Ocelot.Administration source code has been moved out of the Ocelot repository (pull request #2274) and transferred to the Ocelot.Administration.IdentityServer4 repository.
Currently, the Administration feature is solely based on the IdentityServer4 package, whose repository was archived by its owner on July 31, 2024. In this release, the Ocelot team deprecated the Ocelot.Administration.IdentityServer4 extension package after the current Ocelot v24.0 release; however, the repository is/will not be archived, allowing for potential patches in the future.
Commits viewable in compare view.
You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)