Skip to content

Bump Consul and 3 others #1612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump Consul and 3 others #1612

wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 30, 2025

Updated Consul from 1.6.10.7 to 1.7.14.7.

Release notes

Sourced from Consul's releases.

1.7.14.7

What's Changed

New Contributors

Full Changelog: G-Research/consuldotnet@v1.7.14.6...v1.7.14.7

1.7.14.6

What's Changed

Full Changelog: G-Research/consuldotnet@v1.7.14.5...v1.7.14.6

1.7.14.5

What's Changed

New Contributors

Full Changelog: G-Research/consuldotnet@v1.7.14.4...v1.7.14.5

1.7.14.4

What's Changed

New Contributors

Full Changelog: G-Research/consuldotnet@v1.7.14.3...v1.7.14.4

1.7.14.3

What's Changed

Full Changelog: G-Research/consuldotnet@v1.7.14.2...v1.7.14.3

1.7.14.2

What's Changed

Full Changelog: G-Research/consuldotnet@v1.7.14.1...v1.7.14.2

1.7.14.1

What's Changed

New Contributors

Full Changelog: G-Research/consuldotnet@v1.6.10.9...v1.7.14.1

1.6.10.9

1.6.10.9

  • Adding properties: AliasService, AliasNode to AgentServiceCheck class for support: (#​202)
  • Update project url (#​212)
  • Update CI, drop tests for old frameworks, add net7.0 (#​213)

What's Changed

New Contributors

Full Changelog: G-Research/consuldotnet@v1.6.10.8...v1.6.10.9

1.6.10.8

What's Changed

New Contributors

Full Changelog: G-Research/consuldotnet@v1.6.10.7...v1.6.10.8

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Mvc.NewtonsoftJson from 9.0.0 to 9.0.4.

Release notes

Sourced from Microsoft.AspNetCore.Mvc.NewtonsoftJson's releases.

9.0.4

Release

What's Changed

Full Changelog: dotnet/aspnetcore@v9.0.3...v9.0.4

9.0.3

Release

What's Changed

Full Changelog: dotnet/aspnetcore@v9.0.2...v9.0.3

9.0.2

Release

What's Changed

Full Changelog: dotnet/aspnetcore@v9.0.1...v9.0.2

9.0.1

Release

What's Changed

Full Changelog: dotnet/aspnetcore@v9.0.0...v9.0.1

Commits viewable in compare view.

Updated Ocelot from 18.0.0 to 24.0.0.

Release notes

Sourced from Ocelot's releases.

24.0.0

Upgrade to .NET 9 (TFM net9.0, version 24.0) aka .NET 9 release

Milestone: .NET 9
Codenamed: .NET 9
Read the Docs: Ocelot 24.0 with PDF
Target Framework Monikers: net8.0, net9.0

ℹ️ About

On November 12th, 2024, the .NET team announced the release of the .NET 9 framework:

This major release upgrades Ocelot package TFMs to net9.0 in addition to the current net8.0. Thus, the current Ocelot supported frameworks are .NET 8 LTS and .NET 9 STS. According to the .NET Support Policy, the Ocelot team has discontinued support of .NET 6 and .NET 7 by providing the version 23.4.3 which targets those .NET versions.

🔖 Official Notice to the Community Regarding CircleCI

Ocelot's previous CI/CD provider, CircleCI, facilitated professional and seamless development, build processes, and delivery of Ocelot versions for seven years, starting in March 2018. But last year, in January 2025, after patching Ocelot with version 23.4.3, our team encountered legal issues related to CircleCI Co's policies, leading to this CI/CD provider stopping the build process for the Ocelot project. This legal issue and technical incident were unforeseen on our part because Ocelot is open-source software (OSS), and forcibly stopping the project's build process and blocking accounts appears to be an unfortunate breach of OSS principles. We strongly believe that any developer or user, from any country, should be able to use software providers that support the OSS movement by offering free or other cost-free plans and serving the accounts of these users, OSS teams, and OSS projects 24/7, 365 days a year. We consider this legal issue and the resulting technical incidents involving CircleCI to be a serious breach of OSS principles and an act of discrimination against Ocelot users, developers, and customers who rely on Ocelot OSS, ultimately causing delays to the current release. As a team, we do not recommend using CircleCI for OSS projects, as there is no guarantee that these projects will not face discrimination from this U.S. company.

For all developers, team leads, architects, and managers of any OSS projects—at least on GitHub—we recommend utilizing the built-in GitHub Actions CI/CD infrastructure. Since its founding, GitHub has supported OSS projects. Today, GitHub provides 2,000 minutes of free CI/CD build time per month for OSS repositories (public repos). Also, we strongly believe that GitHub will never violate its OSS policies without a notice period, nor fail to inform owners and maintainers that certain policies must be met by Ocelot's owners. In addition, we want to acknowledge that we are monitoring U.S. government regulations. Unfortunately, we must state that some GitHub products are unavailable in certain countries, even if the project is OSS and GitHub claims these products are free for OSS. Since the Ocelot team does not utilize these non-critical products (we prefer to energize our brains rather than rely on AI-driven products), and since the Ocelot project is currently well-served by GitHub Co, the Ocelot team affirms that Ocelot will remain on GitHub as long as its OSS-friendly policies continue. As a team, we hope that GitHub will never enforce extra rules on our project or other OSS projects.
Regardless, we remain on GitHub! octocat

🆕 What's New?

DevOps: The CI/CD infrastructure was migrated from CircleCI to GitHub Actions by @​raman-m

Starting from version 24.0, all pull requests, development commits, and releases will be built using GitHub Actions workflows (documentation). We currently have three workflows: one for pull requests (PR), one for the develop branch (Develop), and one for the main branch (Release). All workflow runs are available on the Actions dashboard.

The PR workflow will track code coverage using Coveralls. After opening a pull request or submitting a new commit to a pull request, Coveralls will publish a short message with the current code coverage once the top commit is built. Considering that Coveralls retains the entire history but does not fail the build if coverage falls below the threshold, all workflows have a built-in 80% threshold, applied internally within the build-cake job, particularly during the "Cake Build" step-action. If the code coverage of a newly opened pull request drops below the 80% threshold, the build-cake job will fail, logging an appropriate message in the "Cake Build" step. For your information, the current code coverage of the Ocelot project is around 85-86%. The coverage threshold is subject to change in upcoming releases. All Coveralls builds can be viewed by navigating to the ThreeMammals/Ocelot project on Coveralls.io.

🆙 What's Updated?

Core:

The main Ocelot package and all extension packages reference net8.0 and net9.0 target framework monikers (TFMs). Refer to TargetFrameworks to verify this. The net6.0 and net7.0 TFMs have been removed. If your project still relies on these outdated TFMs, please continue using version 23.4.3.

Authentication:

Testing of Identity Server Bearer Tokens functionality was stopped due to vulnerabilities reported by Dependabot, specifically the "IdentityServer Open Redirect vulnerability" security issue. More technical details were provided in the 23.4.3 release notes, where we notified the community. Ultimately, issue #​2218 was addressed via pull request #​2274.

Note: In upcoming releases, we plan to utilize the ASP.NET Core Identity framework in our acceptance testing project to align with .NET industry standards. As a result, we intend to replace the IdentityServer4 library with ASP.NET Core Identity, which also supports Bearer tokens, also known as JwtBearerHandler from the Microsoft.AspNetCore.Authentication.JwtBearer namespace.

Administration:

The Ocelot.Administration extension package has been renamed to Ocelot.Administration.IdentityServer4 (it is scheduled for deprecation) to address all IdentityServer4-related vulnerabilities (issue #​2218). The package's source code has been moved out of the Ocelot repository (pull request #​2274) and transferred to the newly created Ocelot.Administration.IdentityServer4 repository.

Note: Currently, the Administration feature is solely based on the IdentityServer4 package, whose repository was archived by its owner on July 31, 2024. The Ocelot team will deprecate the new Ocelot.Administration.IdentityServer4 extension package after the current Ocelot release; however, the repository will not be archived, allowing for potential patches in the future.

Kubernetes:
  1. Answered question #​2256 on "How to provide a host to the Kubernetes service discovery provider?"
    Unfortunately, in the Kubernetes chapter, it was unclear to users how to define a K8s endpoint host in the Configuration due to the implicit reuse of KubeClient, which is created from the pod account during Install-ation. As a team, we decided to add the new AddKubernetes(Action<KubeClientOptions>) method, which handles different user scenarios. It is now possible to provide manually configured KubeClientOptions in C# during Install-ation, but users can also reuse ServiceDiscoveryProvider options from the global configuration, including the Host option to construct the kubernetes endpoint address. The new overloaded AddKubernetes(Action<KubeClientOptions>) method was implemented in pull request #​2257.
  2. In the Ocelot.Provider.Kubernetes extension package, the KubeClient dependency library version was upgraded to 3.0.x, which requires .NET 8.0 and .NET 9.0 TFMs for the current Ocelot version 24.0. KubeClient v3 was internally reviewed and released specifically to meet Ocelot's needs for this release. Thanks to Adam Friedman (@​tintoy) for his collaboration! This package upgrade was implemented in pull request #​2266.
    ... (truncated)

23.4.3

🔥 Hot fixing #​2246 issue (version 23.4.3) aka v23.4.2 patch 📦

Read the Docs: Ocelot 23.4 with PDF
Hot fixed version: 23.4.2
Milestone: November'24

ℹ️ About

🔥 Hot fixed issue: #​2246
❤️ A sincere and heartfelt "Thank You" to Donny Tian, @​donnytian for reporting the bug.

⚠️ Warning

  1. Consider this patch as the last one supporting .NET 6 and 7 frameworks. For more details, refer to the previous version notes.
  2. No further patches for this minor version are expected. The next major release will be .NET 9, version 24.0.

❗ Breaking Changes

Upgrading from 23.4.0-23.4.2 to 23.4.3 introduces no breaking changes. However, some internal interfaces have been updated, which should not introduce IBC for 99.99% of projects. For further information, refer to the source code.

What's Changed

Full Changelog: ThreeMammals/Ocelot@23.4.2...23.4.3

23.4.2

📦 End of .NET 6, 7 Support (version 23.4.2)

Read the Docs: Ocelot 23.4 with PDF
Hot fixed version: 23.4.1
Milestone: November'24

This is the last patched version for .NET 6 and 7 frameworks. The upcoming major release, version 24.0, will target .NET 9 alongside the LTS .NET 8. Projects targeting .NET 6 or 7 should update to this version while considering an upgrade to .NET 8 or 9 in the future.

ℹ️ About

  • All package versions have been updated to latest versions targeting the net6.0 and net7.0 frameworks, along with the LTS net8.0.
  • Dependabot alerts concerning reported vulnerabilities related to IdentityServer4 have not yet been addressed; these will be resolved in the next major release (refer to Warnings further information).

❗ Warning

  1. Releasing a patched 23.4.* is possible.
  2. In the next major version, the Ocelot team will remove references to the IdentityServer4 package from testing projects due to its "Public Archive" status; the version, 4.1.2, was released on July 7, 2021.
  3. The main Ocelot package is not integrated with IdentityServer4, allowing Ocelot users to utilize any authentication provider, as Ocelot's Authentication feature is provider-agnostic.
  4. Our plans to utilize the ASP.NET Core Identity framework in testing projects due to industry standards, instead the IdentityServer4 library.
  5. Following the release of .NET 9, the team will begin the deprecation of the Ocelot extension-packages: Ocelot.Cache.CacheManager, Ocelot.Tracing.Butterfly, and Ocelot.Tracing.OpenTracing.

What's Changed

Full Changelog: ThreeMammals/Ocelot@23.4.1...23.4.2

23.4.1

📦 Routing patch (version 23.4.1)

Read the Docs: Ocelot 23.4 with PDF
Hot fixed version: 23.4.0
Milestone: November'24

❤️ A heartfelt "Thank You" to Guillaume Gnaegi (@​ggnaegi)

ℹ️ About

🔥 Hot fixed issues: #​2165 #​2209 #​2212

What's Changed

Full Changelog: ThreeMammals/Ocelot@23.4.0...23.4.1

23.4.0

🔀 Routing Update (version 23.4.0) aka McDonald's release

Codenamed: McDonald's
Read the Docs: Ocelot 23.4.0

ℹ️ About

This minor release significantly upgrades the Routing feature by supporting embedded placeholders within path segments (between slashes). Additionally, the team has focused on enhancing the performance of Regex objects.

🆕 What's new?

  • Routing: Introducing the new "Embedded Placeholders" feature by @​ggnaegi.
    As of November 2024, Ocelot was unable to process multiple placeholders embedded between two forward slashes. It was also challenging to differentiate the placeholder from other elements within the slashes. For example, /{url}-2/ for /y-2/ would yield {url} = y-2. We are excited to introduce an enhanced method for evaluating placeholders that allows for the resolution of placeholders within complex URLs.
    For additional information, refer to PR #​2200.

🆙 Focus On

Features: Routing, Core, Rate Limiting, Middleware Injection
Documentation for v23.4.0

Honoring 🏅 aka Top Contributors 👏

1st 🥇 goes to Mohsen Rajabi for delivering 1 feature in 12 files changed
2nd 🥈 goes to Jolanta Łukawska for delivering 1 feature in 8 files changed
3rd 🥉 goes to Karim Esskalli for delivering 1 feature in 6 files changed

Starring ⭐ aka Release Influencers :bowtie:

⭐ Mohsen Rajabi, @​EngRajabi
⭐ Jolanta Łukawska, @​jlukawska
⭐ Raman Maksimchuk, @​raman-m
⭐ Karim Esskalli, @​kesskalli
⭐ Guillaume Gnaegi, @​ggnaegi

Features in Release 23.4.0

Logbook
  • 41fc9bd5 by Raman Maksimchuk on Monday, November 18 at 23:40 →
    ... (truncated)

23.3.6

🔥 Hot fixing v23.3.4 (version 23.3.6) aka October'24 release

Read the Docs: Ocelot 23.3
Hot fixed version: 23.3.4
Milestone: October'24

❤️ A heartfelt "Thank You" to Nikolai Masson (@​Niksson) and Nikolay Kuksov (@​kick2nick) for their contributions!

ℹ️ About

This release provides minor bug fixes from the previous 23.3.4 release. All bugs have been addressed in the October'24 milestone.

📓 For projects utilizing the Service Discovery feature, it is recommended to update to this version to benefit from the unstable release 23.3.4, which includes fixes for both Consul and Kube discovery providers.

🧑‍💻 Technical Information

The Ocelot solution encountered a significant issue with the disabled scope validation of services in the DI-container, affecting both testing projects and the core library. Initially, this was not problematic when services were designed as singletons by previous contributors and our team. However, with the introduction of more scoped services by the Ocelot team, it became clear that our testing projects could not adequately handle them.
This patch introduces scope validation across all domains: unit tests, acceptance tests, and the core library itself. We advise always enabling scope validation in your custom Ocelot solutions, especially when dealing with numerous C# overridden classes in the DI-container and any attached custom functionality.

The patch enhances functionality for two primary Service Discovery providers:

  • The Ocelot.Provider.Consul provider. The addressed bug is issue #​2178, reported on October 17, 2024.
    The System.InvalidOperationException error stating "Cannot resolve scoped service 'Ocelot.Provider.Consul.Interfaces.IConsulServiceBuilder' from root provider" has been resolved.
    To clarify, the IConsulServiceBuilder service is a scoped service in DI, injected via the AddConsul() or AddConsul<T>() methods. Therefore, the DefaultConsulServiceBuilder should also be a scoped service, with HttpContext injected to meet your development requirements.
  • The Ocelot.Provider.Kubernetes provider had an issue reported as #​977 on August 1, 2019.
    It involved a System.InvalidOperationException with the message: "Cannot resolve scoped service 'KubeClient.IKubeApiClient' from root provider." This "invalid scopes" error occurred only in development mode, as release mode DLLs do not validate scopes. However, the KubeApiClient is designed to have a scoped lifetime. Acceptance tests passed because scope validation was disabled, and the KubeClient was replaced with a singleton. This inconsistency was identified and reproduced by the old 977 issue. As a temporary solution, the IKubeApiClient was registered as a singleton.
    Looking ahead, our team intends to redesign the Kubernetes provider to have a default service builder that is scoped, similar to the Consul provider.

❗ Breaking Changes

Upgrading from 23.3.4 to 23.3.6 introduces no breaking changes. However, upgrading from 23.3.0 or earlier versions may result in some incompatibilities. For further information, please refer to the release notes of v23.3.4.

Starring ⭐ aka Release Influencers :bowtie:

⭐⭐ Raman Maksimchuk, @​raman-m
⭐ Henrique Holtz, @​henriqueholtz
⭐ Nikolay, @​kick2nick
⭐ Nikolai Masson, @​Niksson
⭐ Emmanuel Ferdman, @​emmanuel-ferdman
⭐ dependabot[bot], @​dependabot

What's Changed

New Contributors

Full Changelog: ThreeMammals/Ocelot@23.3.5...23.3.6

23.3.5

📦 Documentation patch (version 23.3.5), technical release

Read the Docs: Ocelot 23.3
PDF Doc: Ocelot 23.3
Hot fixed version: 23.3.4

ℹ️ About

This documentation patch pertains to HTML and PDF document layouts.
No NuGet packages have been uploaded.

23.3.4

🔥 Hot fixing v23.3 (version 23.3.4) aka Blue Olympic Balumbes release

Codenamed: Blue Olympic Fiend
Read the Docs: Ocelot 23.3
Hot fixed versions: 23.3.0, 23.3.3
Milestone: v23.3 Hotfixes

❤️ A heartfelt "Thank You" to Roman Shevchik and Massimiliano Innocenti for their contributions in testing and reporting the Service Discovery issues, #​2110 and #​2119, respectively!

ℹ️ About

This release de....

Description has been truncated

@dependabot
Bump Consul and 3 others
3629cb7 
Bumps Consul from 1.6.10.7 to 1.7.14.7
Bumps Microsoft.AspNetCore.Mvc.NewtonsoftJson from 9.0.0 to 9.0.4
Bumps Ocelot from 18.0.0 to 24.0.0
Bumps Ocelot.Provider.Consul from 18.0.0 to 24.0.0

---
updated-dependencies:
- dependency-name: Consul
  dependency-version: 1.7.14.7
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: Microsoft.AspNetCore.Mvc.NewtonsoftJson
  dependency-version: 9.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: Ocelot
  dependency-version: 24.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: Ocelot.Provider.Consul
  dependency-version: 24.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Oct 30, 2025
@dependabot dependabot bot mentioned this pull request Oct 30, 2025
Closed
@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 30, 2025

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .net code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant