Repository navigation
chore: Bump Microsoft.SourceLink.GitHub from 10.0.403 to 11.0.100 - #964
Conversation
--- updated-dependencies: - dependency-name: Microsoft.SourceLink.GitHub dependency-version: 11.0.100 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Test Results 44 files ±0 44 suites ±0 37m 32s ⏱️ + 2m 32s Results for commit 772ff8a. ± Comparison against base commit e76b823. This pull request removes 22 and adds 16 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
🚀 Benchmark ResultsCompared to CallbackBenchmarks✅ No changes in memory or relative performance (1 benchmarks) All benchmarks compared to main
Raw resultsBenchmarkDotNet v0.15.8, Linux Ubuntu 26.04.1 LTS (Resolute Raccoon) Intel Xeon Platinum 8370C CPU 2.80GHz (Max: 2.37GHz), 1 CPU, 4 logical and 2 physical cores .NET SDK 11.0.100 [Host] : .NET 11.0.0 (11.0.0, 11.0.26.53018), X64 RyuJIT x86-64-v4 Job=InProcess Toolchain=InProcessEmitToolchain IterationCount=15 LaunchCount=1 WarmupCount=10
CompleteEventBenchmarksRelative performance (how many times as long the other library takes as Mockolate, main → PR)
All benchmarks compared to main
Raw resultsBenchmarkDotNet v0.15.8, Linux Ubuntu 26.04.1 LTS (Resolute Raccoon) AMD EPYC 9V74 3.61GHz, 1 CPU, 4 logical and 2 physical cores .NET SDK 11.0.100 [Host] : .NET 11.0.0 (11.0.0, 11.0.26.53018), X64 RyuJIT x86-64-v4 Job=InProcess Toolchain=InProcessEmitToolchain IterationCount=15 LaunchCount=1 WarmupCount=10
CompleteIndexerBenchmarks✅ No changes in memory or relative performance (2 benchmarks) All benchmarks compared to main
Raw resultsBenchmarkDotNet v0.15.8, Linux Ubuntu 26.04.1 LTS (Resolute Raccoon) AMD EPYC 7763 3.24GHz, 1 CPU, 4 logical and 2 physical cores .NET SDK 11.0.100 [Host] : .NET 11.0.0 (11.0.0, 11.0.26.53018), X64 RyuJIT x86-64-v3 Job=InProcess Toolchain=InProcessEmitToolchain IterationCount=15 LaunchCount=1 WarmupCount=10
CompleteMethodBenchmarks✅ No changes in memory or relative performance (2 benchmarks) All benchmarks compared to main
Raw resultsBenchmarkDotNet v0.15.8, Linux Ubuntu 26.04.1 LTS (Resolute Raccoon) AMD EPYC 9V45 4.54GHz, 1 CPU, 4 logical and 2 physical cores .NET SDK 11.0.100 [Host] : .NET 11.0.0 (11.0.0, 11.0.26.53018), X64 RyuJIT x86-64-v4 Job=InProcess Toolchain=InProcessEmitToolchain IterationCount=15 LaunchCount=1 WarmupCount=10
CompletePropertyBenchmarks✅ No changes in memory or relative performance (2 benchmarks) All benchmarks compared to main
Raw resultsBenchmarkDotNet v0.15.8, Linux Ubuntu 26.04.1 LTS (Resolute Raccoon) AMD EPYC 9V74 3.69GHz, 1 CPU, 4 logical and 2 physical cores .NET SDK 11.0.100 [Host] : .NET 11.0.0 (11.0.0, 11.0.26.53018), X64 RyuJIT x86-64-v4 Job=InProcess Toolchain=InProcessEmitToolchain IterationCount=15 LaunchCount=1 WarmupCount=10
MockCreationBenchmarks✅ No changes in memory or relative performance (1 benchmarks) All benchmarks compared to main
Raw resultsBenchmarkDotNet v0.15.8, Linux Ubuntu 26.04.1 LTS (Resolute Raccoon) Intel Xeon Platinum 8370C CPU 2.80GHz (Max: 3.37GHz), 1 CPU, 4 logical and 2 physical cores .NET SDK 11.0.100 [Host] : .NET 11.0.0 (11.0.0, 11.0.26.53018), X64 RyuJIT x86-64-v4 Job=InProcess Toolchain=InProcessEmitToolchain IterationCount=15 LaunchCount=1 WarmupCount=10
|
SourceLink 11 depends on System.IO.Hashing 11, which has no net8.0 build; its netstandard2.0 build brings an internal CallerArgumentExpressionAttribute polyfill that makes the cref to the framework attribute ambiguous (CS0419) on net8.0.
|
… from 10.0.403 to 11.0.100 (#964) by dependabot[bot]
… from 10.0.403 to 11.0.100 (#964) by dependabot[bot]



Updated Microsoft.SourceLink.GitHub from 10.0.403 to 11.0.100.
Release notes
Sourced from Microsoft.SourceLink.GitHub's releases.
11.0.100
You can build .NET 11.0 from the repository by cloning the release tag
v11.0.100and 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-11.0.100-rtm.26529.118.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.11.0.100-rc.3.26522.148
You can build .NET 11.0 RC 3 from the repository by cloning the release tag
v11.0.100-rc.3.26522.148and 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-11.0.100-rc.3.26522.148.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.11.0.100-rc.2.26504.105
You can build .NET 11.0 RC 2 from the repository by cloning the release tag
v11.0.100-rc.2.26504.105and 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
11.0.100-rc.1.26425.128
You can build .NET 11.0 RC 1 from the repository by cloning the release tag
v11.0.100-rc.1.26425.128and 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
11.0.100-preview.7.26381.103
You can build .NET 11.0 Preview 7 from the repository by cloning the release tag
v11.0.100-preview.7.26381.103and 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
11.0.100-preview.6.26359.118
You can build .NET 11.0 Preview 6 from the repository by cloning the release tag
v11.0.100-preview.6.26359.118and 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
11.0.100-preview.5.26302.115
You can build .NET 11.0 Preview 5 from the repository by cloning the release tag
v11.0.100-preview.5.26302.115and 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
11.0.100-preview.4.26230.115
You can build .NET 11.0 Preview 4 from the repository by cloning the release tag
v11.0.100-preview.4.26230.115and 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
11.0.100-preview.3.26207.106
You can build .NET 11.0 Preview 3 from the repository by cloning the release tag
v11.0.100-preview.3.26207.106and 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
11.0.100-preview.2.26159.112
You can build .NET 11.0 Preview 2 from the repository by cloning the release tag
v11.0.100-preview.2.26159.112and 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
11.0.100-preview.1.26104.118
You can build .NET 11.0 Preview 1 from the repository by cloning the release tag
v11.0.100-preview.1.26104.118and 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
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.
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 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)