Conversation
thomhurst
added
dependencies
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review: chore(deps): update dependency dotnet-sdk to v10.0.200
This is a routine automated dependency update from Renovate Bot, bumping the .NET SDK from 10.0.103 to 10.0.200 (a patch update within the 10.0.x line).
Changes Reviewed
global.json— root-level SDK version bumptest/ModularPipelines.TestsForTests/global.json— matching SDK version bump in the test project
Assessment
This is a clean, well-structured dependency update. A few observations:
-
Consistency — Both
global.jsonfiles are updated together, which is correct. Having mismatched SDK versions between the root and the test project would cause build inconsistencies. -
rollForward policy — Both files retain
"rollForward": "latestMinor"and"allowPrerelease": false, which is a sound configuration for a production library — it avoids accidental adoption of preview builds. -
Patch-to-minor jump — The version moves from
10.0.103(patch band) to10.0.200(the first release of the 10.0.2xx feature band). Feature band updates in .NET can occasionally include tooling changes (e.g., MSBuild behavior, NuGet client updates) beyond pure bug fixes, so it's worth confirming CI passes cleanly before merging. -
Auto-merge is enabled — Given this is a feature-band update rather than a pure patch, it may be worth reviewing CI results before auto-merge proceeds, especially for a library project where SDK tooling differences could affect build output or NuGet package metadata.
No architectural concerns. The change is minimal, targeted, and follows the existing project conventions. ✅
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
88addc1 to
86904b4
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
changed the title
There was a problem hiding this comment.
Code Review: chore(deps): update dotnet monorepo
This is a Renovate Bot automated dependency update. A previous review was posted for an earlier commit; this review covers the full current diff.
Changes Reviewed
| File | Change |
|---|---|
Directory.Packages.props |
Microsoft.Build 18.3.3 → 18.4.0 (minor) |
global.json |
dotnet-sdk 10.0.103 → 10.0.200 (feature band) |
test/ModularPipelines.TestsForTests/global.json |
dotnet-sdk 10.0.103 → 10.0.200 (feature band) |
Assessment
The changes are clean and well-scoped. A few notes:
-
Microsoft.Build 18.4.0 — A minor version bump. Minor releases in
Microsoft.Buildcan introduce new MSBuild features or behavior changes (e.g., new evaluation semantics, property/item function additions). Since this project includes MSBuild-related tooling and the Options Generator, it's worth confirming the build pipeline and analyzer projects still produce the same output post-update. The CI run will validate this. -
dotnet-sdk 10.0.200 — As noted in the prior review, this crosses a .NET feature band boundary (1xx → 2xx). Feature bands are tooling-level updates that can carry changes to MSBuild, NuGet, Roslyn integration, and templating. This is a higher-impact change than a pure patch. No action needed beyond confirming CI passes.
-
Consistency — Both
global.jsonfiles are updated together, which is correct. A mismatch between the root andtest/ModularPipelines.TestsForTests/would cause hard-to-diagnose build issues. -
rollForward policy — Retained as
latestMinor/allowPrerelease: falseacross both files. This remains a sound configuration.
No architectural concerns. The update is minimal, targeted, and consistent with project conventions. The combination of the MSBuild minor bump and SDK feature band bump in a single PR is worth a close eye on CI, but there are no issues with the changes themselves. ✅
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
86904b4 to
04cf3c4
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
There was a problem hiding this comment.
Code Review: chore(deps): update dotnet monorepo
Two previous reviews have been posted on earlier commits. This review covers the full current diff and checks whether prior observations remain applicable.
Changes in Current Diff
| File | Change |
|---|---|
Directory.Packages.props |
Microsoft.Build 18.3.3 → 18.4.0 (minor) |
Directory.Packages.props |
Microsoft.Extensions.TimeProvider.Testing 10.3.0 → 10.4.0 (minor) |
global.json |
dotnet-sdk 10.0.103 → 10.0.200 (feature band) |
test/ModularPipelines.TestsForTests/global.json |
dotnet-sdk 10.0.103 → 10.0.200 (feature band) |
Follow-up on Previous Review Notes
- SDK feature band bump (10.0.1xx → 10.0.2xx) — flagged in both prior reviews. No action needed from the author; CI results are the right gate here.
- Microsoft.Build 18.4.0 — flagged in the second review for potential MSBuild behavior changes. Again, CI is the correct validation mechanism.
- Both concerns are inherent to automated dependency updates, not issues with how the PR is structured.
New in This Diff: Microsoft.Extensions.TimeProvider.Testing 10.3.0 → 10.4.0
This package provides FakeTimeProvider and related test utilities from dotnet/extensions. The 10.x line tracks the .NET 10 major version, so this is a standard minor increment. No behavioral concerns expected — this library is test-only and does not affect production runtime behavior.
Overall Assessment
The PR is clean, minimal, and consistent:
- All version bumps are from trusted first-party Microsoft sources
global.jsonfiles are updated in sync (root + test project), avoiding potential SDK mismatch issuesrollForward: latestMinorandallowPrerelease: falseare preserved- No manual configuration or logic changes — purely mechanical version bumps
No architectural concerns. Previous review notes have been accounted for; nothing outstanding. Looks good to merge once CI is green. ✅
There was a problem hiding this comment.
Code Review: chore(deps): update dotnet monorepo
Two previous reviews have been posted on earlier commits. This review covers the full current diff and checks whether prior observations remain applicable.
Changes in Current Diff
| File | Change |
|---|---|
Directory.Packages.props |
Microsoft.Build 18.3.3 → 18.4.0 (minor) |
Directory.Packages.props |
Microsoft.Extensions.TimeProvider.Testing 10.3.0 → 10.4.0 (minor) |
global.json |
dotnet-sdk 10.0.103 → 10.0.200 (feature band) |
test/ModularPipelines.TestsForTests/global.json |
dotnet-sdk 10.0.103 → 10.0.200 (feature band) |
Follow-up on Previous Review Notes
- SDK feature band bump (10.0.1xx → 10.0.2xx) — flagged in both prior reviews. No action needed from the author; CI results are the right gate here.
- Microsoft.Build 18.4.0 — flagged in the second review for potential MSBuild behavior changes. CI is the correct validation mechanism.
- Both concerns are inherent to automated dependency updates, not issues with how the PR is structured.
New in This Diff: Microsoft.Extensions.TimeProvider.Testing 10.3.0 → 10.4.0
This package provides FakeTimeProvider and related test utilities from dotnet/extensions. The 10.x line tracks the .NET 10 major version, so this is a standard minor increment. No behavioral concerns expected — this library is test-only and does not affect production runtime behavior.
Overall Assessment
The PR is clean, minimal, and consistent:
- All version bumps are from trusted first-party Microsoft sources
global.jsonfiles are updated in sync (root + test project), avoiding potential SDK mismatch issuesrollForward: latestMinorandallowPrerelease: falseare preserved- No manual configuration or logic changes — purely mechanical version bumps
No architectural concerns. Previous review notes have been accounted for; nothing outstanding. Looks good to merge once CI is green. ✅
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
04cf3c4 to
76ade54
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
There was a problem hiding this comment.
Code Review: chore(deps): update dotnet monorepo (latest commit)
Four previous reviews have been posted on earlier commits. This review covers the full current diff on the latest commit (76ade549) and notes what is new since the last review.
Full Change Summary
| File | Package | Change | Type |
|---|---|---|---|
Directory.Packages.props |
Microsoft.Build |
18.3.3 → 18.4.0 |
minor |
Directory.Packages.props |
Microsoft.Extensions.Caching.Memory |
10.0.4 → 10.0.5 |
patch |
Directory.Packages.props |
Microsoft.Extensions.DependencyInjection |
10.0.4 → 10.0.5 |
patch |
Directory.Packages.props |
Microsoft.Extensions.Hosting |
10.0.4 → 10.0.5 |
patch |
Directory.Packages.props |
Microsoft.Extensions.Http |
10.0.4 → 10.0.5 |
patch |
Directory.Packages.props |
Microsoft.Extensions.TimeProvider.Testing |
10.3.0 → 10.4.0 |
minor |
Directory.Packages.props |
Microsoft.SourceLink.GitHub |
10.0.200 → 10.0.201 |
patch |
Directory.Packages.props |
System.CommandLine |
2.0.4 → 2.0.5 |
patch |
global.json |
dotnet-sdk | 10.0.103 → 10.0.200 |
feature band |
test/ModularPipelines.TestsForTests/global.json |
dotnet-sdk | 10.0.103 → 10.0.200 |
feature band |
New Since Last Review
The latest commit adds the following packages not covered previously:
Microsoft.Extensions.Caching.Memory/DependencyInjection/Hosting/Http10.0.5 — Coordinated patch updates across the Microsoft.Extensions family. These are pure bug-fix releases with no API surface changes expected. Low risk.Microsoft.SourceLink.GitHub10.0.200 → 10.0.201 — Patch bump to the SourceLink tooling that embeds source file links in NuGet packages. This affects debug symbols/PDB metadata but has no runtime impact. Low risk.System.CommandLine2.0.4 → 2.0.5 — Patch bump.System.CommandLineis used for CLI argument parsing in this project. Patch releases in this package are typically bug fixes; no breaking changes expected.
Carryover from Previous Reviews
- dotnet-sdk 10.0.200 feature band bump — previously flagged; CI is the correct gate.
- Microsoft.Build 18.4.0 minor bump — previously flagged; CI validation applies.
- Microsoft.Extensions.TimeProvider.Testing 10.4.0 — previously reviewed; no concerns.
Overall Assessment
The PR is clean, well-scoped, and consistent with project conventions:
- All updates are from first-party Microsoft sources via Renovate Bot
- The
Microsoft.Extensions.*packages are updated as a coordinated group, which avoids version skew between interdependent packages - Both
global.jsonfiles remain in sync rollForward: latestMinorandallowPrerelease: falseare preserved- No logic or configuration changes — purely mechanical version bumps
No architectural concerns. Previous review notes have been addressed by the coordinated nature of automated updates. Looks good to merge once CI is green. ✅
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
76ade54 to
8bcebf3
Compare
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
7236fe5 to
c27f83b
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
There was a problem hiding this comment.
Code Review: Automated Dependency Update
This is a clean, routine Renovate Bot dependency update. No architectural or design concerns.
Changes
- 8 NuGet package bumps in
Directory.Packages.props(patch/minor) - .NET SDK
10.0.103→10.0.201(feature band bump) in bothglobal.jsonfiles
Assessment
No issues found. This is well-structured and low-risk.
A few observations worth noting:
-
Centralized package management is correctly used. All version bumps are consolidated in
Directory.Packages.props— no scattered<PackageReference Version="...">entries that could drift. Good pattern, consistently applied. -
SDK feature band bump (10.0.1xx → 10.0.2xx). Feature bands can affect tooling behavior (workload manifests, included analyzers, template versions). The
rollForward: "latestMinor"policy inglobal.jsonwas already configured to tolerate this. Bothglobal.jsonfiles are updated in sync, which prevents the silent CI inconsistency that can occur when root and test projects use different SDKs. No action needed — CI is the right gate. -
Microsoft.Build18.4.0 (minor bump). MinorMicrosoft.Buildreleases can introduce new MSBuild evaluation semantics. Given that this repo includes MSBuild-related tooling (tools/ModularPipelines.OptionsGenerator/) and analyzer projects, CI output for those is worth a quick check. This is not a blocker — just the highest-risk update in the batch. -
Microsoft.Extensions.TimeProvider.Testing10.3.0 → 10.4.0. Minor bumps here can occasionally shift timing behavior in time-provider-dependent test scenarios. CI covers this. -
All other updates (
Microsoft.Extensions.*patches,SourceLink,System.CommandLine) are patch-level and carry negligible risk.
Recommendation
Approve and merge once CI passes. The diff is correctly scoped, consistent with the repo's dependency management strategy, and all prior review concerns have been addressed.
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
c27f83b to
c0fdf71
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
There was a problem hiding this comment.
Code Review: chore(deps): update dotnet monorepo
This is a Renovate Bot consolidated dependency update covering the .NET SDK and several NuGet packages.
Changes Reviewed
global.json (root + test project):
- .NET SDK:
10.0.103→10.0.201
Directory.Packages.props:
| Package | Old | New | Type |
|---|---|---|---|
Microsoft.Build |
18.3.3 | 18.4.0 | minor |
Microsoft.Extensions.Caching.Memory |
10.0.4 | 10.0.5 | patch |
Microsoft.Extensions.DependencyInjection |
10.0.4 | 10.0.5 | patch |
Microsoft.Extensions.Hosting |
10.0.4 | 10.0.5 | patch |
Microsoft.Extensions.Http |
10.0.4 | 10.0.5 | patch |
Microsoft.Extensions.TimeProvider.Testing |
10.3.0 | 10.4.0 | minor |
Microsoft.SourceLink.GitHub |
10.0.200 | 10.0.201 | patch |
System.CommandLine |
2.0.4 | 2.0.5 | patch |
Assessment
This is a clean, routine dependency update — no concerns.
A few observations worth noting:
-
SDK jump skips 10.0.200 — The SDK goes from
10.0.103directly to10.0.201, which indicates 10.0.200 was likely handled (or superseded) by a prior Renovate PR. This is fine and expected with consolidation runs. -
Consistency maintained — Both
global.jsonfiles (root andtest/ModularPipelines.TestsForTests/) are updated in lockstep. Mismatched SDK pins between projects would cause subtle build inconsistencies, so this is the correct approach. -
rollForward: latestMinor+allowPrerelease: false— These settings remain unchanged and are the right policy for a production library targeting stable tooling. -
Centralized version management — Using
Directory.Packages.propsfor all NuGet versions is the right pattern here. A single-line bump per package with no risk of version drift across projects. -
Microsoft.Buildminor bump (18.3.3 → 18.4.0) — This is the only non-patch NuGet update. MSBuild minor versions occasionally contain API additions, but since this project uses it as a tool dependency (for the options generator), no breaking changes are expected.
Approved. ✅
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
c0fdf71 to
4d4bbe9
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
There was a problem hiding this comment.
Code Review: chore(deps): update dotnet monorepo
This is a Renovate Bot consolidated dependency update. No logic changes — purely version bumps in centralized package management files.
Changes Reviewed
global.json (root + test/ModularPipelines.TestsForTests/):
- .NET SDK:
10.0.103→10.0.201(feature band bump, same major/minor)
Directory.Packages.props:
| Package | Old | New | Type |
|---|---|---|---|
Microsoft.Build |
18.3.3 | 18.4.0 | minor |
Microsoft.Extensions.Caching.Memory |
10.0.4 | 10.0.6 | patch |
Microsoft.Extensions.DependencyInjection |
10.0.4 | 10.0.6 | patch |
Microsoft.Extensions.Hosting |
10.0.4 | 10.0.6 | patch |
Microsoft.Extensions.Http |
10.0.4 | 10.0.6 | patch |
Microsoft.Extensions.TimeProvider.Testing |
10.3.0 | 10.4.0 | minor |
Microsoft.SourceLink.GitHub |
10.0.200 | 10.0.202 | patch |
System.CommandLine |
2.0.4 | 2.0.6 | patch |
Assessment
No issues. This is a clean, well-structured dependency update.
A few observations:
-
Version skipping is expected here. Several packages jump two patch versions (e.g.,
10.0.4→10.0.6,2.0.4→2.0.6). This is normal when Renovate consolidates multiple pending updates into a single PR — there is no concern about missing intermediate changes. -
Centralized package management is correctly used. All bumps are in
Directory.Packages.props, which is the right place for a project using Central Package Management. Individual.csprojfiles correctly remain untouched. -
Both
global.jsonfiles are updated consistently. Keeping the root andtest/ModularPipelines.TestsForTests/global.jsonin sync avoids SDK mismatch issues during CI. -
Microsoft.Build18.4.0 is a minor bump with notable improvements (terminal logger quiet mode fix, multiple binary log support). These are additive changes and pose no breaking risk for a consumer of the package. -
allowPrerelease: falseis retained in bothglobal.jsonfiles — the correct stance for a production library.
Safe to merge.
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
4d4bbe9 to
b283930
Compare
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
There was a problem hiding this comment.
Code Review: chore(deps): update dotnet monorepo (latest commit)
This is a follow-up to the previous reviews on this PR. The diff has evolved since the last review; this review covers the full current diff and highlights what is new.
Full Change Summary
| File | Package | From | To | Type |
|---|---|---|---|---|
Directory.Packages.props |
Microsoft.Build |
18.3.3 | 18.4.0 | minor |
Directory.Packages.props |
Microsoft.Extensions.Caching.Memory |
10.0.4 | 10.0.6 | patch |
Directory.Packages.props |
Microsoft.Extensions.DependencyInjection |
10.0.4 | 10.0.6 | patch |
Directory.Packages.props |
Microsoft.Extensions.Hosting |
10.0.4 | 10.0.6 | patch |
Directory.Packages.props |
Microsoft.Extensions.Http |
10.0.4 | 10.0.6 | patch |
Directory.Packages.props |
Microsoft.Extensions.TimeProvider.Testing |
10.3.0 | 10.4.0 | minor |
Directory.Packages.props |
Microsoft.SourceLink.GitHub |
10.0.200 | 10.0.202 | patch |
Directory.Packages.props |
System.CommandLine |
2.0.4 | 2.0.6 | patch |
global.json (root) |
dotnet-sdk | 10.0.103 | 10.0.202 | patch within 10.0.2xx band |
test/ModularPipelines.TestsForTests/global.json |
dotnet-sdk | 10.0.103 | 10.0.202 | patch within 10.0.2xx band |
What is New Since the Last Review
- dotnet-sdk
10.0.201→10.0.202— an additional patch within the 10.0.2xx feature band. This is a pure bug-fix release within the same band; lower risk than the10.0.1xx→10.0.2xxfeature band jump that was flagged in earlier reviews. Microsoft.Extensions.Caching.Memory/DependencyInjection/Hosting/Http10.0.5→10.0.6— one additional patch increment for the coordinated Microsoft.Extensions group. These packages are always updated together to prevent version skew, which is the correct approach given their interdependencies.Microsoft.SourceLink.GitHub10.0.201→10.0.202— patch bump; affects only debug symbol metadata embedded in NuGet packages, no runtime impact.System.CommandLine2.0.5→2.0.6— patch bump; no breaking changes expected.
Status of Prior Review Observations
All prior observations remain applicable and unchanged:
- The SDK feature band jump (10.0.1xx → 10.0.2xx) flagged in earlier reviews is still relevant; CI is the correct gate.
Microsoft.Build18.4.0 remains the only NuGet minor bump; CI validates any MSBuild behavior changes.Microsoft.Extensions.TimeProvider.Testing10.4.0 is test-only; no production impact.
Overall Assessment
The PR is clean and well-structured. The additional increments in this latest commit are all lower-risk than the changes already reviewed. No concerns:
- All version bumps are centralized in
Directory.Packages.props— no drift across individual.csprojfiles. - Both
global.jsonfiles remain in sync; this is important for reproducible builds when the root and the test sub-project are resolved independently. rollForward: latestMinorandallowPrerelease: falseare preserved across both files.- All updates originate from trusted first-party Microsoft sources via Renovate Bot automation.
No architectural concerns. Safe to merge once CI is green.
thomhurst
force-pushed
the
renovate/dotnet-monorepo
branch
from
b283930 to
41c9111
Compare
There was a problem hiding this comment.
Code Review: chore(deps): update dotnet monorepo
This is a routine automated Renovate Bot dependency update, expanding on the previously reviewed SDK bump. The PR has since grown to include multiple NuGet package updates.
Changes Since Previous Review
A prior review covered only the dotnet-sdk bump to 10.0.200. This PR now includes:
- SDK bumped further to
10.0.202 - 8 NuGet package updates in
Directory.Packages.props
Assessment
All changes look clean and well-structured.
dotnet-sdk: 10.0.103 → 10.0.202 — This crosses a feature band (100-series → 200-series), but rollForward: latestMinor is configured in both global.json files, making this safe. Both files are updated in sync, which is correct.
NuGet packages:
Microsoft.Extensions.*(Caching, DI, Hosting, Http): 10.0.4 → 10.0.6 — patch bumps, minimal riskMicrosoft.Extensions.TimeProvider.Testing: 10.3.0 → 10.5.0 — minor bump on a test-only package, no production impactMicrosoft.Build: 18.3.3 → 18.4.0 — minor bump; release notes show bug fixes (terminal logger, UTF-8 encoding opt-out) and telemetry changes. No breaking changes expected for this project's usage.Microsoft.SourceLink.GitHub: 10.0.200 → 10.0.202 — patch, purely build-timeSystem.CommandLine: 2.0.4 → 2.0.6 — patch bump
All packages are managed centrally through Directory.Packages.props, which is the correct pattern for Central Package Management. No version pinning inconsistencies or skipped packages observed.
Codacy reports 0 new issues. This PR is safe to merge.
2 participants
This PR contains the following updates:
18.3.3→18.4.010.0.4→10.0.610.0.4→10.0.610.0.4→10.0.610.0.4→10.0.610.3.0→10.5.010.0.200→10.0.2022.0.4→2.0.610.0.103→10.0.202Release Notes
dotnet/msbuild (Microsoft.Build)
v18.4.0What's Changed
1305085by @dotnet-bot in #129821305236by @dotnet-bot in #129841307838by @dotnet-bot in #130031307982by @dotnet-bot in #130101312418by @dotnet-bot in #130531313748by @dotnet-bot in #130751313792by @dotnet-bot in #130811316676by @dotnet-bot in #131071316744by @dotnet-bot in #131171318654by @dotnet-bot in #13128Full Changelog: dotnet/msbuild@v18.3.3...v18.4.0
dotnet/extensions (Microsoft.Extensions.TimeProvider.Testing)
v10.4.0This release advances the AI abstractions with new hosted file, web search, and reasoning content types, stabilizes MCP and tool approval APIs, adds streaming latency metrics to OpenTelemetry instrumentation, and delivers bug fixes across caching, data ingestion, and resource monitoring.
Experimental API Changes
Now Stable
MEAI001) #7299FakeLogCollector.GetLogsAsync(CancellationToken)is now stable (previouslyEXTEXP0003) #7332New Experimental APIs
AddExtendedHttpClientLoggingoverloads withwrapHandlersPipelineparameter (EXTEXP0013) #7231Removed Experimental APIs
MEAI001) #7353What's Changed
AI
Telemetry and Observability
HTTP Resilience and Diagnostics
Diagnostics, Health Checks, and Resource Monitoring
Data Ingestion
Caching
Test Improvements
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.3.0...v10.4.0
dotnet/dotnet (Microsoft.SourceLink.GitHub)
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
dotnet/sdk (dotnet-sdk)
v10.0.201: .NET 10.0.5Compare Source
Release
v10.0.200: .NET 10.0.4Release
v10.0.105Compare Source
v10.0.104Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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 has been generated by Renovate Bot.