Skip to content

Bump the nuget group with 6 updates #142

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
Closed
wants to merge 1 commit into from
Closed

Bump the nuget group with 6 updates #142

wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 28, 2025 •
edited
Loading

Updated BenchmarkDotNet from 0.14.0 to 0.15.2.

Release notes

Sourced from BenchmarkDotNet's releases.

0.15.2

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.2.html

Highlights

  • The most significant update in this release is the enhanced accuracy of the memory diagnoser (#​2562). This improvement resolves the issue of incorrectly reported memory allocations (#​1542, #​2582).
  • We have introduced a new feature that allows users to sort benchmark jobs in numerical order (#​2768, #​2770).
  • Benchmark validation has been improved (#​2771).
  • An issue with non-persistent auto-generated JobId has been fixed (#​2777).

0.15.1

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.1.html

Highlights

0.15.0

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.0.html

Commits viewable in compare view.

Updated CacheManager.Microsoft.Extensions.Caching.Memory from 1.2.0 to 2.0.0.

Release notes

Sourced from CacheManager.Microsoft.Extensions.Caching.Memory's releases.

2.0.0

Breaking Changes

  • CacheManager.Microsoft.Extensions.Logging is not a separated package anymore. Logging is now part of the Core package.
  • CacheManager.Memcached is not supported anymore
  • CacheManager.Couchbase is not supported anymore
  • CacheManager.Web is not supported anymore

What's Changed

New Contributors

Other Notes

Testing with Microsoft.Garnet

For testing and benchmarking, this project is now using Microsoft.Garnet, which allows to create a Redis server which runs in process and is easy to setup.
This has some limitations though and before you use Microsoft.Garnet in production, be aware that key space notifications are not supported yet.

Commits viewable in compare view.

Updated Microsoft.Extensions.Caching.Memory from 9.0.2 to 9.0.7.

Release notes

Sourced from Microsoft.Extensions.Caching.Memory's releases.

9.0.7

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.6...v9.0.7

9.0.6

Bug Fixes

  • Read messages from binlog if process output is missing build finished message (#​114676)
    Improves reliability of the WebAssembly build process by reading messages from the binlog when the process output does not contain the expected build finished message, preventing build failures in certain scenarios.

  • Fix debugger app hangs related to thread exit (#​114917)
    Resolves an issue where applications could hang during debugging when threads exit, ensuring smoother debugging experiences and preventing deadlocks.

  • [Mono] Workaround MSVC miscompiling sgen_clz (#​114903)
    Addresses a compiler miscompilation issue in MSVC affecting the Mono garbage collector, improving runtime stability and correctness on affected platforms.

  • Do not set the salt or info if they are NULL for OpenSSL HKDF (#​114877)
    Fixes a cryptographic issue by ensuring that the salt or info parameters are not set when they are NULL in OpenSSL HKDF, preventing potential errors or unexpected behavior in key derivation.

  • [Test Only] Fix Idn tests (#​115032)
    Corrects issues in Internationalized Domain Name (Idn) tests, ensuring accurate and reliable test results for domain name handling.

  • JIT: revised fix for fp division issue in profile synthesis (#​115026)
    Provides a more robust fix for floating-point division issues in JIT profile synthesis, improving numerical accuracy and preventing incorrect calculations.

  • Handle OSSL 3.4 change to SAN:othername formatting (#​115361)
    Updates certificate handling to accommodate changes in Subject Alternative Name (SAN) formatting introduced in OpenSSL 3.4, ensuring compatibility and correct parsing of certificates.

  • [Mono] Fix c11 ARM64 atomics to issue full memory barrier (#​115635)
    Fixes atomic operations on ARM64 in Mono to issue a full memory barrier, ensuring correct synchronization and preventing subtle concurrency bugs.

Performance Improvements

  • [WinHTTP] Certificate caching on WinHttpHandler to eliminate extra call to Custom Certificate Validation (#​114678)
    Improves HTTP performance by caching certificates in WinHttpHandler, reducing redundant calls to custom certificate validation and speeding up secure connections.

  • Improve distribute_free_regions (#​115167)
    Optimizes memory management by enhancing the algorithm for distributing free memory regions, leading to better memory utilization and potentially improved application performance.

Technical Improvements

  • Strip trailing slash from source dir for cmake4 (#​114905)
    Refines build scripts by removing trailing slashes from source directories when using CMake 4, preventing potential build path issues and improving build reliability.

  • Don't expose TrustedCertificatesDirectory() and StartNewTlsSessionContext() to NetFx (#​114995)
    Restricts certain internal APIs from being exposed to .NET Framework, reducing surface area and preventing unintended usage.

  • Add support for more libicu versions (#​115376)
    Expands compatibility by supporting additional versions of the International Components for Unicode (ICU) library, enhancing globalization features across more environments.

Infrastructure

  • Run outerloop pipeline only for release branches, not staging/preview (#​115011)
    Optimizes CI/CD resources by limiting the outerloop pipeline to run only on release branches, reducing unnecessary test runs and speeding up development workflows.

... (truncated)

9.0.5

Release

What's Changed

9.0.4

Release

What's Changed

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

9.0.3

Release

What's Changed

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

Commits viewable in compare view.

Updated Microsoft.NET.ILLink.Analyzers from 7.0.100-1.23211.1 to 7.0.100-1.23401.1.

Release notes

Sourced from Microsoft.NET.ILLink.Analyzers's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 17.12.0 to 17.13.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

17.13.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v17.12.0...v17.13.0

Commits viewable in compare view.

Updated ZiggyCreatures.FusionCache from 2.1.0 to 2.3.0.

Release notes

Sourced from ZiggyCreatures.FusionCache's releases.

2.3.0

🔑 Access the cache key in the factory context

Community user @​posledam and others asked for the ability to access the cache key in the factory context, to be able to work with it while going to the database or similar, without creating a closure with the lambda.

So that's what I added, but there's a catch here: FusionCache provides automatic cache key manipulation with things like CacheKeyPrefix usually in conjunction with things like Named Caches, so it would be nice to access both the original one and the processed one.

Therefore I added both of them in the factory context, and it can be used like this:

cache.GetOrSet<string>(
  "foo",
  (ctx, token) => {
    ctx.Key; // THE (PROCESSED) CACHE KEY
    ctx.OriginalKey; // THE (ORIGINAL) CACHE KEY
  }
);

See here for the original issue, and here for the design issue.

⚙️ New InternalStrings options

FusionCache automatically handles a lot of things for us, and to do that it may need to manipulate some strings used internally like the cache key or the backplane channel name.

For example to use the CacheName to automatically separate data in a shared cache when used in conjunction with other FusionCache instances, or the set of special cache keys used with Tagging or the way wire format versioning is handled to automatically avoid errors when evolving the internal data structures.

In these cases some special characters are used as separators.

This is all good and well, but recently community user @​stebet started working on a NATS version of the backplane (and that's awesome!) and he noticed that some of these special characters create issues on NATS, which has some reserved characters that have special meaning or cannot be used anyway.

Because of this I'm adding a new set of options specifically for changing the set of internal strings used by FusionCache, so that it's possible to work with systems like NATS and avoid issues.

So now we have a new InternalStrings option inside of FusionCacheOptions where we can set strings like:

  • TagCacheKeyPrefix
  • ClearRemoveTag
  • DistributedCacheWireFormatSeparator
  • BackplaneWireFormatSeparator
  • and more

It can be used like this:

var options = new FusionCacheOptions()
{
  // ...
  InternalStrings = {
    TagCacheKeyPrefix = "tag__",
    ClearRemoveTag = "clear_remove"
    // ...
  }
 ... (truncated)

## 2.2.0

## 🎯 Changes in multi-targeting

Some time ago I started enabling multi-targeting on FusionCache: I didn't do that because I needed to special case some parts of the code, but just because I wanted to reduce the amount of explicit dependencies for certain TFMs after a request from the community.

But recently community user @​nick-randal noticed in #​416 some potential issues: long story short, from now on FusionCache will have explicit targeting only for currently supported TFMs (which today means no more .NET 3.1, .NET 6 or .NET 7) and for them it will have the minimum set of explicit dependencies.

But wait: does this mean that those older versions of .NET wil not be able to use FusionCache anymore?

Absolutely not: since FusionCache targets .NET Standard 2.0, this means that ANY version of .NET compatible with .NET Standard 2.0 (meaning: all versions) will still be able to use FusionCache, just without an explicit "support statement", since those versions are anyway not supported anymore, not even by Microsoft itself.

See [here](https://github.com/ZiggyCreatures/FusionCache/issues/416) and [here](https://github.com/ZiggyCreatures/FusionCache/issues/425) for the original issues.

## 🚀 Make the AOT support official

FusionCache has been AOT compatible for a long time, which is already good.

I just need to make that more "official" by declaring it in the csproj, enabling analyzers, create a test console app and, in general, do everything that's needed. And that's what I did.

Thanks to community user @​digital88 for pointing that out.

See [here](https://github.com/ZiggyCreatures/FusionCache/discussions/439) and [here](https://github.com/ZiggyCreatures/FusionCache/issues/449) for the original issues.

## 🔀 Expose the current distributed cache, if any

Currently, given a `FusionCache` instance, it's only possible to know if there is a distributed cache level (L2) via the `bool HasDistributedCache { get; }` property, not which one it is.

Community user @​angularsen asked to expose it in #​443 .

Historically I've been hesitant to expose internals, but at this point I think I can let this one go.

So now there's a new `IDistributedCache? DistributedCache { get; }` property that expose the `IDistributedCache` instance being used, if any.

See [here](https://github.com/ZiggyCreatures/FusionCache/issues/443) and [here](https://github.com/ZiggyCreatures/FusionCache/issues/446) for the original issues.

> [!WARNING]
> This is _technically_ a breaking change, but since nobody has custom `IFusionCache` implementations and I updated both (`FusionCache` and `NullFusionCache`), I think this is fine.

## 📢 Expose the current backplane, if any

Same as above, but for the backplane.

So now there's a new a new `IFusionCacheBackplane? Backplane { get; }` property that expose the `IFusionCacheBackplane` instance being used, if any.

See [here](https://github.com/ZiggyCreatures/FusionCache/issues/443) and [here](https://github.com/ZiggyCreatures/FusionCache/issues/445) for the original issues.

> [!WARNING]
> This is _technically_ a breaking change, but since nobody has custom `IFusionCache` implementations and I updated both (`FusionCache` and `NullFusionCache`), I think this is fine.

## 😶 Add DI support for `NullFusionCache`

 ... (truncated)

## 2.2.0-preview-1

## 🎯 Changes in multi-targeting

Some time ago I started enabling multi-targeting on FusionCache: I didn't do that because I needed to special case some parts of the code, but just because I wanted to reduce the amount of explicit dependencies for certain TFMs fater after a request from the community.

But recently community user @​nick-randal noticed in #​416 some potential issues: long story short, from now on FusionCache will have explicit targeting only for currently supported TFMs (which today means no more .NET 3.1, .NET 6 or .NET 7) and for them it will have the minimum set of explicit dependencies.

But wait: does this mean that those older versions of .NET wil not be able to use FusionCache anymore?

Absolutely not: since FusionCache targets .NET Standard 2.0, this means that ANY version of .NET compatible with .NET Standard 2.0 (meaning: all versions) will still be able to use FusionCache, just without an explicit "support statement", since those versions are anyway not supported anymore, not even by Microsoft itself.

See [here](https://github.com/ZiggyCreatures/FusionCache/issues/416) and [here](https://github.com/ZiggyCreatures/FusionCache/issues/425) for the original issues.

## 🚀 Make the AOT support official

FusionCache has been AOT compatible for a long time, which is already good.

I just need to make that more "official" by declaring it in the csproj, enabling analyzers, create a test console app and, in general, do everything that's needed. And that's what I did.

Thanks to community user @​digital88 for pointing that out.

See [here](https://github.com/ZiggyCreatures/FusionCache/discussions/439) and [here](https://github.com/ZiggyCreatures/FusionCache/issues/449) for the original issues.

## 🔀 Expose the current distributed cache, if any

Currently, given a `FusionCache` instance, it's only possible to know if there is a distributed cache level (L2) via the `bool HasDistributedCache { get; }` property, not which one it is.

Community user @​angularsen asked to expose it in #​443 .

Historically I've been hesitant to expose internals, but at this point I think I can let this one go.

So now there's a new `IDistributedCache? DistributedCache { get; }` property that expose the `IDistributedCache` instance being used, if any.

See [here](https://github.com/ZiggyCreatures/FusionCache/issues/443) and [here](https://github.com/ZiggyCreatures/FusionCache/issues/446) for the original issues.

> [!WARNING]
> This is _technically_ a breaking change, but since nobody has custom `IFusionCache` implementations and I updated both (`FusionCache` and `NullFusionCache`), I think this is fine.

## 📢 Expose the current backplane, if any

Same as above, but for the backplane.

So now there's a new a new `IFusionCacheBackplane? Backplane { get; }` property that expose the `IFusionCacheBackplane` instance being used, if any.

See [here](https://github.com/ZiggyCreatures/FusionCache/issues/443) and [here](https://github.com/ZiggyCreatures/FusionCache/issues/445) for the original issues.

> [!WARNING]
> This is _technically_ a breaking change, but since nobody has custom `IFusionCache` implementations and I updated both (`FusionCache` and `NullFusionCache`), I think this is fine.

See here for the original issue.

 ... (truncated)

Commits viewable in [compare view](https://github.com/ZiggyCreatures/FusionCache/compare/v2.1.0...v2.3.0).
</details>

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions


</details>

@dependabot
Bump the nuget group with 6 updates
e6f98ae 
Bumps BenchmarkDotNet from 0.14.0 to 0.15.2
Bumps CacheManager.Microsoft.Extensions.Caching.Memory from 1.2.0 to 2.0.0
Bumps Microsoft.Extensions.Caching.Memory from 9.0.2 to 9.0.7
Bumps Microsoft.NET.ILLink.Analyzers from 7.0.100-1.23211.1 to 7.0.100-1.23401.1
Bumps Microsoft.NET.Test.Sdk from 17.12.0 to 17.13.0
Bumps ZiggyCreatures.FusionCache from 2.1.0 to 2.3.0

---
updated-dependencies:
- dependency-name: BenchmarkDotNet
  dependency-version: 0.15.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: CacheManager.Microsoft.Extensions.Caching.Memory
  dependency-version: 2.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget
- dependency-name: Microsoft.Extensions.Caching.Memory
  dependency-version: 9.0.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.NET.ILLink.Analyzers
  dependency-version: 7.0.100-1.23401.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 17.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: ZiggyCreatures.FusionCache
  dependency-version: 2.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
...

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 Jul 28, 2025
@dependabot dependabot bot mentioned this pull request Jul 28, 2025
Closed
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 4, 2025

Looks like these dependencies are no longer updatable, so this is no longer needed.

@dependabot dependabot bot closed this Aug 4, 2025
@dependabot dependabot bot deleted the dependabot/nuget/examples/Weather/nuget-ed1d133a14 branch August 4, 2025 07:58
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