Repository navigation
Conversation
Bumps Microsoft.Extensions.DependencyInjection.Abstractions from 9.0.22 to 9.0.23 Bumps Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0 Bumps Microsoft.SourceLink.GitHub from 10.0.403 to 10.0.404 Bumps WireMock.Net from 2.30.0 to 2.31.0 --- updated-dependencies: - dependency-name: Microsoft.Extensions.DependencyInjection.Abstractions dependency-version: 9.0.23 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-minor-patch - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-minor-patch - dependency-name: Microsoft.SourceLink.GitHub dependency-version: 10.0.404 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-minor-patch - dependency-name: WireMock.Net dependency-version: 2.31.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…et8 로 닫는 근거를 핀 옆에 Dependabot #1048 이 csproj 만 올려 doc-facts(필수 체크)가 CLAUDE.md:267·274·278 을 불일치로 막았다. - CLAUDE.md 표 셋: DI.Abstractions 9.0.23 · Microsoft.NET.Test.Sdk 18.12.0 · WireMock.Net 2.31.0. - 같은 날 온 메이저 둘(#1049 · #1051)을 닫는 근거를 핀 옆 csproj 주석에 둔다(68행이 쓰는 방식): - DI.Abstractions 11.0.0 의 nuspec 대상 묶음은 net10.0 · net11.0 · net462 · netstandard2.0/2.1 — net8.0 이 없다(9.0.23 에는 있다). - SourceLink.GitHub 11.0.100 은 net10.0 · net472 에 System.IO.Hashing 11.0.0 을 더한다. #1051 의 net8.0 레인 빌드가 「doesn't support net8.0」 경고를 냈다(로그 6줄 — 10.0.404 인 #1048 은 0줄). 10.0.403 은 net8.0 태스크를 싣는다. - .claude/rules/dotnet.md 69행: 「10.x 만 닫는다」 → 「DI 는 9.x 위, SourceLink 는 10.x 위를 닫는다」. 예산(7323B)이 꽉 차 있어 근거를 csproj 로 보내고 줄은 그 안에서 다시 썼다. - 로컬 `dotnet build -c Release` 경고 0 · 오류 0, check-docs --strict 통과. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…10.x → 11.0.0 으로 옮겨진다 앞 커밋의 「11.x adds System.IO.Hashing 11」은 거짓이었다 — 10.x 도 이미 그 패키지에 의존한다. 다시 쟀다(nuget nuspec): - SourceLink.GitHub 10.0.403 → System.IO.Hashing 10.0.14, 10.0.404 → 10.0.15, 11.0.100 → 11.0.0. - System.IO.Hashing 10.0.15 대상 묶음 = net462 · net8.0 · net9.0 · net10.0 · netstandard2.0, 11.0.0 = net10.0 · net11.0 · net462 · netstandard2.0 — net8.0 이 없다. 그래서 경고의 원인은 「새 의존」이 아니라 「의존의 판이 net8.0 을 버린 것」이다. 결론(10.x 에 머문다)은 같다. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…과 다시 재는 법 독립 리뷰(Grok)가 짚었다: 앞 커밋의 「Majors above 9.x stay closed: the 11.0.0 nuspec has no net8.0 group」은 11.0.0 만 재고 10.x 까지 같은 이유로 묶었다. 다시 쟀다(nuget nuspec): - DI.Abstractions 10.0.0 · 10.0.15 대상 묶음 = net462 · net8.0 · net9.0 · net10.0 · netstandard2.0/2.1 — net8.0 이 **있다**. 그러니 10.x 를 닫은 이유는 다른 것이다. - 그 이유는 PR #57 의 close 코멘트(2026-07-15)다: net8.0 대상에 net10 시대 메이저는 기능상 이득이 없어 9.x 에 머문다, 9.x 패치는 받는다 — 그리고 `@dependabot ignore this major version`. - 11.0.0 은 그 위에 net8.0 묶음 자체가 없다. 주석에 두 이유를 갈라 적고, 되살릴 조건(TFM 이동 · SourceLink 는 11.x 의 System.IO.Hashing 이 net8.0 묶음을 다시 가질 때)과 다시 재는 주소(nuspec)를 붙였다. 로컬 `dotnet build -c Release` 경고 0 · 오류 0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 13, 2026
xzawed
deleted the
dependabot/nuget/dotnet/src/Xzawed.Keycloak.Sdk/dotnet-minor-patch-fc8d77caa9
branch
November 13, 2026 04:44
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 Microsoft.Extensions.DependencyInjection.Abstractions from 9.0.22 to 9.0.23.
Release notes
Sourced from Microsoft.Extensions.DependencyInjection.Abstractions's releases.
9.0.23
Release
What's Changed
Full Changelog: dotnet/runtime@v9.0.21...v9.0.23
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.12.0
Security fix
This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.12.0
18.11.1
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0.Fixed in:
Microsoft.TestPlatform.CLI18.11.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.11.1
Commits viewable in compare view.
Updated Microsoft.SourceLink.GitHub from 10.0.403 to 10.0.404.
Release notes
Sourced from Microsoft.SourceLink.GitHub's releases.
10.0.404
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.404and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.404-servicing.26529.119.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archives use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.Commits viewable in compare view.
Updated WireMock.Net from 2.30.0 to 2.31.0.
Release notes
Sourced from WireMock.Net's releases.
2.31.0
What's Changed
Full Changelog: wiremock/WireMock.Net@2.30.0...2.31.0
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