Repository navigation
Bump the nuget-minor-patch group with 3 updates - #153
Merged
David Burg (daviburg) merged 1 commit intoSep 29, 2026
Merged
David Burg (daviburg) merged 1 commit into
David Burg (daviburg) merged 1 commit into
Conversation
Bumps ICSharpCode.Decompiler from 11.0.0.9375 to 11.1.0.9782 Bumps MSTest from 4.4.0 to 4.4.1 Bumps ZiggyCreatures.FusionCache from 2.8.0 to 2.9.0 --- updated-dependencies: - dependency-name: ICSharpCode.Decompiler dependency-version: 11.1.0.9782 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: MSTest dependency-version: 4.4.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: ZiggyCreatures.FusionCache dependency-version: 2.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Copilot started reviewing on behalf of
Microsoft Azure (Azure)
September 29, 2026 16:35
View session
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The dependency updates are compatible with the projects’ .NET 8 targets and existing usage.
Review effort: Balanced
Findings: None
What changed in this PR
Updates runtime and test dependencies to current minor/patch releases.
Changes:
- Updates ICSharpCode.Decompiler and FusionCache.
- Updates MSTest.
| File | Description |
|---|---|
Server/SdkLspServer.csproj |
Updates decompiler and cache packages. |
Server.Tests/Server.Tests.csproj |
Updates MSTest to 4.4.1. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
David Burg (daviburg)
approved these changes
Sep 29, 2026
David Burg (daviburg)
deleted the
dependabot/nuget/Server.Tests/main/nuget-minor-patch-7d96a9f184
branch
September 29, 2026 17:36
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 ICSharpCode.Decompiler from 11.0.0.9375 to 11.1.0.9782.
Release notes
Sourced from ICSharpCode.Decompiler's releases.
11.1
Want to learn how we built the Avalonia port of ILSpy? Join us October 6th for Move over, WPF! Avalonia for X-Plat Desktop Apps (with a lot of AI help)
A major focus of this release was to find the small (and not so small) bugs of the decompiler via a revamp of our testing by adding two new tools that allow mass-testing (for more information see
TestTools/README.md):nugetfuzz: downloads packages from nuget.org and runs them through a DEBUG build ofilspycmd(sanity checks/assertions enabled). It records: crash, assertion fail, warnings in the decompiler output (as comment "IL_<nnnn>: ...") as well as any residue of compiler-generated identifiers in C# code (hints at missing language feature/pattern support).decompdiff: runs an assembly through two different versions of the decompiler (driven viailspycmd) and calculates a diff of the generated source code.You should see better decompilation results as an effect of this push and the general push of fixing previously reported decompiler bugs by users.
New Language Features
User Interface
Contributions
Performance
... (truncated)
Commits viewable in compare view.
Updated MSTest from 4.4.0 to 4.4.1.
Release notes
Sourced from MSTest's releases.
4.4.1
See the release notes here
Commits viewable in compare view.
Updated ZiggyCreatures.FusionCache from 2.8.0 to 2.9.0.
Release notes
Sourced from ZiggyCreatures.FusionCache's releases.
2.9.0
🦅 Eager Refresh now also checks L2
Community member @sfhb24 noticed that during an Eager Refresh the L2 was not being checked.
Now, this is admittedly not a huge thing per se, because of 2 reasons:
In both these cases, the extra L2 check during an eager refresh would not be necessary.
Having said that, an L1+L2 setup without a backplane or a distributed locker may also be common, and in that case the new L2 check in the eager refresh window can in fact be helpful in reducing the amount of factory executions even more.
Long story short: I just implemented it!
See here for the issue.
🔒 Fix for memory locker + Eager Refresh edge case
If a factory fails when executed in the background during an eager refresh, FusionCache already takes care of everything and correctly releases the potentially acquired locks (memory and/or distributed), and this is good.
But community member @joaopbnogueira noticed a peculiar edge case: if the factory is not one marked with the
asynckeyword AND it throws an exception, the memory lock is not being released properly.Or, to better say, "was not". Because now this has been fixed.
Thanks João for spotting this.
See here for the issue.
🔒 Fix for distributed locker + skip L1 edge case
Community member @joaopbnogueira also noticed another peculiar scenario, specifically when a
MemoryCachewrite fails (yep, it can happen, true story).Here's an example of it:
MemroyCacheis being used as the L1SizeLimitSizespecifiedSizeLimitit's mandatory for every entry to specify aSize)In this scenario a distributed lock may not have been released.
But fear no more: this does not hapen anymore!
See here for the issue.
🧼 Fix for
Clear(false)+ Fail-Safe... (truncated)
Commits viewable in compare view.
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 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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