chore(deps): update dotnet monorepo to v10#140
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
@CalvinWilkinson This is a major change; assigned to you. |
7f2930c to
c6caf3f
Compare
c6caf3f to
b6de724
Compare
b6de724 to
bc5550e
Compare
bc5550e to
2f89675
Compare
2f89675 to
d214c40
Compare
d214c40 to
1d7a9cf
Compare
1d7a9cf to
e9d907a
Compare
e9d907a to
6e9e2f1
Compare
6e9e2f1 to
14fb783
Compare
14fb783 to
d0389b0
Compare
d0389b0 to
f394010
Compare
cc43d38 to
4dcea82
Compare
4dcea82 to
3934d7a
Compare
3934d7a to
25432e1
Compare
25432e1 to
36c1b64
Compare
36c1b64 to
5a26343
Compare
5a26343 to
7f7b18d
Compare
7f7b18d to
2ebb589
Compare
2ebb589 to
92753c1
Compare
601e025 to
e86e6d1
Compare
a6bc6bf to
7ecca1c
Compare
6f06ab1 to
1b5fe44
Compare
1b5fe44 to
e89770d
Compare
51dcc63 to
6edf21a
Compare
| datasource | package | from | to | | ---------- | ----------------------------------- | ----- | -------- | | nuget | Microsoft.CodeAnalysis.NetAnalyzers | 8.0.0 | 10.0.301 | | nuget | Microsoft.Extensions.Hosting | 7.0.1 | 10.0.9 | | docker | mcr.microsoft.com/dotnet/sdk | 7.0 | 10.0 |
6edf21a to
c7fbf3b
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:
8.0.0→10.0.3017.0.1→10.0.97.0→10.07.0→10.0Release Notes
dotnet/dotnet (Microsoft.CodeAnalysis.NetAnalyzers)
v10.0.301: .NET 10.0.9 / 10.0.301You can build .NET 10.0 from the repository by cloning the release tag
v10.0.301and 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.300: .NET 10.0.8 / 10.0.300You can build .NET 10.0 from the repository by cloning the release tag
v10.0.300and 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.204: .NET 10.0.8 / 10.0.204You can build .NET 10.0 from the repository by cloning the release tag
v10.0.204and 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.203: .NET 10.0.7 / 10.0.203You can build .NET 10.0 from the repository by cloning the release tag
v10.0.203and 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.202: .NET 10.0.6 / 10.0.202You can build .NET 10.0 from the repository by cloning the release tag
v10.0.202and 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.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.109: .NET 10.0.9 / 10.0.109You can build .NET 10.0 from the repository by cloning the release tag
v10.0.109and 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.108: .NET 10.0.8 / 10.0.108You can build .NET 10.0 from the repository by cloning the release tag
v10.0.108and 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.107: .NET 10.0.7 / 10.0.107You can build .NET 10.0 from the repository by cloning the release tag
v10.0.107and 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.106: .NET 10.0.6 / 10.0.106You can build .NET 10.0 from the repository by cloning the release tag
v10.0.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
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.102v10.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.v9.0.0: .NET 9.0.0You can build .NET 9.0 from the repository by cloning the release tag
v9.0.0and 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
Configuration
📅 Schedule: (UTC)
🚦 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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.