Skip to content

Update dotnet monorepo to v10 (major) #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dotnet monorepo to v10 (major) #51

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 14, 2023 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
Microsoft.AspNetCore.Mvc.Testing (source) 7.0.1 -> 10.0.1 age confidence nuget major
Microsoft.AspNetCore.OpenApi (source) 7.0.0 -> 10.0.1 age confidence nuget major
Microsoft.AspNetCore.TestHost (source) 7.0.0 -> 10.0.1 age confidence nuget major
Microsoft.Extensions.DependencyInjection (source) 7.0.0 -> 10.0.1 age confidence nuget major
dotnet-sdk 7.0.101 -> 10.0.101 age confidence dotnet-sdk major

Release Notes

dotnet/dotnet (Microsoft.AspNetCore.Mvc.Testing)

v10.0.1

v9.0.7: .NET 9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 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

v9.0.6: .NET 9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 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

v9.0.5: .NET 9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 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

v9.0.4: .NET 9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 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

v9.0.3: .NET 9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 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

v9.0.2: .NET 9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 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

v9.0.1: .NET 9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 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

v9.0.0: .NET 9.0.0

You can build .NET 9.0 from the repository by cloning the release tag v9.0.0 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

v8.0.18: .NET 8.0.18

You can build .NET 8.0 from the repository by cloning the release tag v8.0.18 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

v8.0.17: .NET 8.0.17

You can build .NET 8.0 from the repository by cloning the release tag v8.0.17 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

v8.0.16: .NET 8.0.16

You can build .NET 8.0 from the repository by cloning the release tag v8.0.16 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

v8.0.15: .NET 8.0.15

You can build .NET 8.0 from the repository by cloning the release tag v8.0.15 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

v8.0.14: .NET 8.0.14

You can build .NET 8.0 from the repository by cloning the release tag v8.0.14 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

v8.0.13: .NET 8.0.13

You can build .NET 8.0 from the repository by cloning the release tag v8.0.13 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

v8.0.12: .NET 8.0.12

You can build .NET 8.0 from the repository by cloning the release tag v8.0.12 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

v8.0.11: .NET 8.0.11

You can build .NET 8.0 from the repository by cloning the release tag v8.0.11 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

v8.0.10: .NET 8.0.10

You can build .NET 8.0 from the repository by cloning the release tag v8.0.10 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

v8.0.8: .NET 8.0.8

You can build .NET 8.0 from the repository by cloning the release tag v8.0.8 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

v8.0.7: .NET 8.0.7

You can build .NET 8.0 from the repository by cloning the release tag v8.0.7 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

v8.0.6: .NET 8.0.6

You can build .NET 8.0 from the repository by cloning the release tag v8.0.6 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

v8.0.5: .NET 8.0.5

You can build .NET 8 from the repository by cloning the release tag v8.0.5 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

v8.0.4: .NET 8.0.4

You can build .NET 8.0 from the repository by cloning the release tag v8.0.4 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

v8.0.3: .NET 8.0.3

You can build .NET 8.0 from the repository by cloning the release tag v8.0.3 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

v8.0.2: .NET 8.0.2

You can build .NET 8.0 from the repository by cloning the release tag v8.0.2 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

v8.0.1: .NET 8.0.1

You can build .NET 8.0 from the repository by cloning the release tag v8.0.1 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://dotnet.microsoft.com/download/dotnet/release-key-2023.asc

v8.0.0: .NET 8.0

You can build .NET 8.0 from the repository by cloning the release tag v8.0.0 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://dotnet.microsoft.com/download/dotnet/release-key-2023.asc

dotnet/sdk (dotnet-sdk)

v10.0.101: .NET 10.0.1

Compare Source

Release

What's Changed

Full Changelog: dotnet/sdk@v10.0.100...v10.0.101

v10.0.100: .NET 10.0.0

Compare Source

Release

What's Changed

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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 2a329fa to 4aba228 Compare January 10, 2024 03:38
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 3 times, most recently from fe231dc to 766a972 Compare February 16, 2024 11:05
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 3 times, most recently from 9e755fe to db75fcc Compare March 15, 2024 12:11
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 1014579 to ee3e9ac Compare April 10, 2024 14:40
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from ee3e9ac to c8d0431 Compare May 14, 2024 20:26
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from d3782a9 to a44160d Compare May 29, 2024 20:01
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from a44160d to da72788 Compare June 11, 2024 22:02
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 622c0de to 36ffb5e Compare July 10, 2024 03:49
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 3 times, most recently from b2efcda to e3dd3b2 Compare August 16, 2024 06:30
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from e3dd3b2 to c33bc54 Compare September 25, 2024 13:35
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from c33bc54 to 5a5e8d5 Compare October 8, 2024 16:12
@qodo-code-review
Copy link

qodo-code-review bot commented Oct 8, 2024

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: build-test-pull-request

Failed stage: Build, Test and Pack [❌]

Failure summary:

The action failed because the required .NET SDK version specified in the global.json file is not
installed:

  • The global.json file specifies version 8.0.402, which is not installed.
  • Installed versions are 6.0.425, 7.0.410, and 8.0.401.
  • The action suggests installing the 8.0.402 .NET SDK or updating the global.json to match an
    installed SDK version.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

432:  global.json file: /home/runner/work/SimCube.Spartan/SimCube.Spartan/global.json
433:  Installed SDKs:
434:  Install the [8.0.402] .NET SDK or update [/home/runner/work/SimCube.Spartan/SimCube.Spartan/global.json] to match an installed SDK.
435:  Learn about SDK resolution:
436:  https://aka.ms/dotnet/sdk-not-found
437:  6.0.425 [/usr/share/dotnet/sdk]
438:  7.0.410 [/usr/share/dotnet/sdk]
439:  8.0.401 [/usr/share/dotnet/sdk]
440:  ##[error]Process completed with exit code 145.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 5a5e8d5 to 40b6532 Compare October 9, 2024 15:47
    @qodo-code-review
    Copy link

    qodo-code-review bot commented Oct 9, 2024

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: build-test-pull-request

    Failed stage: Build, Test and Pack [❌]

    Failure summary:

    The action failed because the required .NET SDK version specified in the global.json file is not
    installed:

  • The global.json file specifies version 8.0.403.
  • The installed SDK versions are 6.0.425, 7.0.410, and 8.0.402.
  • The required version 8.0.403 is missing, causing the process to exit with code 145.

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

432:  global.json file: /home/runner/work/SimCube.Spartan/SimCube.Spartan/global.json
433:  Installed SDKs:
434:  Install the [8.0.403] .NET SDK or update [/home/runner/work/SimCube.Spartan/SimCube.Spartan/global.json] to match an installed SDK.
435:  Learn about SDK resolution:
436:  https://aka.ms/dotnet/sdk-not-found
437:  6.0.425 [/usr/share/dotnet/sdk]
438:  7.0.410 [/usr/share/dotnet/sdk]
439:  8.0.402 [/usr/share/dotnet/sdk]
440:  ##[error]Process completed with exit code 145.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 40b6532 to 1e3bef8 Compare November 12, 2024 19:40
    @renovate renovate bot changed the title Update dotnet monorepo to v8 (major) Update dotnet monorepo (major) Nov 12, 2024
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 1e3bef8 to 5e7508b Compare November 13, 2024 17:46
    @renovate renovate bot changed the title Update dotnet monorepo (major) Update dotnet monorepo to v9 (major) Nov 13, 2024
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from a2ff118 to 586243a Compare January 15, 2025 02:13
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from b68fe02 to 0d3e812 Compare February 12, 2025 06:45
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 4a3c173 to af66bb1 Compare March 12, 2025 16:42
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from af66bb1 to 39dc088 Compare March 19, 2025 17:12
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from e94c459 to 271bd09 Compare April 9, 2025 23:05
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 239a894 to fb8a976 Compare May 14, 2025 16:26
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 032d044 to e80c7d4 Compare June 11, 2025 08:01
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 0be7c94 to 9ae3135 Compare July 9, 2025 12:37
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 9ae3135 to fa483eb Compare July 18, 2025 06:53
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from a38e153 to ed7184c Compare August 5, 2025 21:37
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from ede35e9 to 86479c3 Compare September 9, 2025 21:38
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 872169a to 5b9bcaa Compare October 14, 2025 22:06
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 4f53f23 to 61a5759 Compare November 11, 2025 16:33
    @renovate renovate bot changed the title Update dotnet monorepo to v9 (major) Update dotnet monorepo (major) Nov 11, 2025
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 61a5759 to 309b1ed Compare November 12, 2025 13:49
    @renovate renovate bot changed the title Update dotnet monorepo (major) Update dotnet monorepo to v10 (major) Nov 12, 2025
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 309b1ed to 2ac9aeb Compare December 9, 2025 19:37
    @renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 2ac9aeb to e83d333 Compare December 10, 2025 15:36
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Reviewers

    No reviews

    Assignees

    No one assigned

    Labels

    breaking dependencies

    Projects

    None yet

    Milestone

    No milestone

    Development

    Successfully merging this pull request may close these issues.

    1 participant