chore(deps): update dotnet monorepo (major)#144
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Conversation
c725747 to
d7e19d6
Compare
9db97ec to
23367ce
Compare
23367ce to
3153408
Compare
444c68c to
718d113
Compare
88f8dd0 to
1e8c823
Compare
1e8c823 to
6eece9e
Compare
c516c46 to
a185a94
Compare
0d1ca0f to
c7a40cf
Compare
0228de4 to
e7e565d
Compare
ee4a97c to
002a763
Compare
002a763 to
df4a269
Compare
df4a269 to
9251182
Compare
9251182 to
1a36782
Compare
feecd32 to
4d86fca
Compare
9f57885 to
f19065a
Compare
9cb6c98 to
7fb283a
Compare
7fb283a to
beeb713
Compare
beeb713 to
bea54fb
Compare
e95d5ff to
dbebd6f
Compare
dbebd6f to
4cf2963
Compare
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.
This PR contains the following updates:
3.3.4→5.3.03.11.0→5.3.03.11.0→5.3.09.0.0→10.0.2018.0.0→10.0.201Release Notes
dotnet/roslyn (Microsoft.CodeAnalysis.CSharp.Workspaces)
v4.0.1: .NET 6.0.1Release
dotnet/dotnet (Microsoft.CodeAnalysis.NetAnalyzers)
v10.0.201: .NET 10.0.5 / 10.0.201You can build .NET 10.0 from the repository by cloning the release tag
v10.0.201and 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
v10.0.200: .NET 10.0.4 / 10.0.200You can build .NET 10.0 from the repository by cloning the release tag
v10.0.200and 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
v10.0.105: .NET 10.0.5 / 10.0.105You can build .NET 10.0 from the repository by cloning the release tag
v10.0.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
v10.0.104: .NET 10.0.4 / 10.0.104You can build .NET 10.0 from the repository by cloning the release tag
v10.0.104and 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
v10.0.103: .NET 10.0.3 / 10.0.103You can build .NET 10.0 from the repository by cloning the release tag
v10.0.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 is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023
v10.0.101: .NET 10.0.1 / 10.0.101You can build .NET 10.0 from the repository by cloning the release tag
v10.0.101and 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
v10.0.100: .NET 10.0.0 / 10.0.100You can build .NET 10.0 from the repository by cloning the release tag
v10.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
To produce artifacts with the .NET 10 GA version strings, users must pass the branding argument to the build:
--branding rtm.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.