Skip to content

Bump Microsoft.SourceLink.GitHub from 10.0.403 to 11.0.100 - #2

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Microsoft.SourceLink.GitHub-11.0.100
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Microsoft.SourceLink.GitHub-11.0.100

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 12, 2026

Copy link
Copy Markdown
Contributor

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.100 and 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 use 0: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.148 and 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 use 0: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.105 and 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.128 and 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.103 and 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.118 and 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.115 and 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.115 and 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.106 and 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.112 and 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.118 and 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.404 and 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 use 0: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 compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---
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>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 12, 2026
@mahach666

Copy link
Copy Markdown
Contributor

@dependabot ignore this major version

@mahach666

Copy link
Copy Markdown
Contributor

Closing: SourceLink 11.x pulls System.IO.Hashing 11.0.0, which does not support net8.0 and adds build warnings for the net8.0 targets. 11.x is now ignored in .github/dependabot.yml.

@mahach666 mahach666 closed this Nov 12, 2026
@mahach666
mahach666 deleted the dependabot/nuget/Microsoft.SourceLink.GitHub-11.0.100 branch November 12, 2026 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant