Skip to content

⬆️ update dotnet-sdk to v10.0.301 #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

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

⬆️ update dotnet-sdk to v10.0.301 #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion global.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"sdk": {
"rollForward": "feature",
"version": "10.0.203"
"version": "10.0.301"

@coderabbitai coderabbitai Bot Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

SDK version violates coding guidelines.

The coding guideline specifies that ".NET SDK version is pinned to 10.0.102 in global.json and rolls forward within the feature band." This change updates the version to 10.0.301, which conflicts with the documented policy.

Please verify whether:

  1. The guideline needs to be updated to reflect a new SDK version policy, or
  2. This PR should revert to the guideline-specified version (10.0.102)

As per coding guidelines: ".NET SDK version is pinned to 10.0.102 in global.json and rolls forward within the feature band."

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@global.json` at line 4, global.json's SDK "version" was changed to "10.0.301"
which violates the repo guideline that pins the .NET SDK to "10.0.102" (rolling
forward within the feature band); either revert the "version" field in
global.json back to "10.0.102" (restore the value in the "version" property) or,
if the policy has changed, update the coding guideline text to reflect the new
pinned SDK (and document the new pinned value and roll-forward behavior).
Confirm which option is intended, then make the corresponding change: modify the
global.json "version" value to 10.0.102 for a revert, or update the guideline to
state the new pinned SDK value and any roll-forward rules.

Source: Coding guidelines

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify .NET SDK version 10.0.301 exists and check for known issues

# Check if the SDK version is available
echo "Checking .NET SDK version 10.0.301..."
curl -s "https://dotnetcli.blob.core.windows.net/dotnet/Sdk/10.0.301/dotnet-sdk-10.0.301-linux-x64.tar.gz" -I | head -n 1

# Also check the releases page for 10.0.x versions
echo -e "\nChecking available .NET 10 SDK releases..."
curl -s "https://dotnetcli.azureedge.net/dotnet/release-metadata/10.0/releases.json" | jq -r '.releases[] | select(.sdks != null) | .sdks[]? | select(.version | startswith("10.0")) | .version' | sort -V | tail -10

Repository: Spillgebees/Transmodel

Length of output: 255

🌐 Web query:

.NET SDK 10.0.301 release notes

💡 Result:

The.NET SDK 10.0.301 was released on June 9, 2026 [1]. It was included as part of the.NET 10.0.9 release [1]. Key details regarding this release: - Release Date: June 9, 2026 [1]. - Included Runtimes: This SDK includes.NET Runtime 10.0.9, ASP.NET Core Runtime 10.0.9, and.NET Desktop Runtime 10.0.9 [2]. - Visual Studio Integration: This SDK is included in Visual Studio 18.7.0 [2]. - Language Support: The SDK supports C# 14.0, F# 10.0, and Visual Basic 17.13 [2]. You can access the official release notes and further details via the.NET GitHub repository [1].

Citations:

🌐 Web query:

.NET SDK 10.0.301 known issues

💡 Result:

As of June 10, 2026,.NET SDK 10.0.301 has been released [1]. Because this version is very recent, official documentation for specific known issues unique to 10.0.301 is currently evolving [2]. Users are encouraged to consult the official.NET 10 Known Issues repository for the most up-to-date tracking [2]. General issues reported in the 10.0.3xx series (including 10.0.300) that may persist or remain relevant include: Performance and Build Regressions: There have been reports of build and restore performance regressions when using.slnx solutions compared to earlier 10.0.2xx versions [3]. Analyzer False Positives: Users have reported new false-positive CA1825 warnings in 10.0.300 [4]. These warnings may appear unexpectedly and break builds configured with treat-warnings-as-errors [4]. A known workaround is to refactor code to use explicit collection initializers instead of array literals where appropriate [4]. MSBuild Error Clarity: Issues have been noted regarding unclear error messaging (e.g., NETSDK1013 or MSB4044) when a TargetFramework is missing or improperly configured in project files, which can make debugging project infrastructure difficult [5]. Workload Management: As documented for the 10.0.1xx series, issues with dotnet workload commands after package manager upgrades remain a potential area of concern for users managing custom workloads [2]. For the latest status, mitigations, and bug tracking, refer to the official.NET Core GitHub repository release notes and issue tracker [2][1].

Citations:

🌐 Web query:

10.0.301 dotnet sdk servicing status support policy

💡 Result:

As of June 10, 2026, the.NET SDK 10.0.301 is a supported version of the.NET 10 release [1]. The following points summarize its servicing status and the applicable support policy: 1. Support Status:.NET 10 is a Long Term Support (LTS) release that reached general availability on November 11, 2025, and is supported until November 14, 2028 [2][3][4]. 2. Servicing Requirement: To remain in a supported state, you must use the latest available servicing update for your specific version [5][6]. Because.NET servicing updates are cumulative, Microsoft recommends regularly installing the most recent patches to ensure you have all security and reliability fixes [5][3]. 3. Servicing Policy: Servicing updates are released on a monthly cadence, typically on "Patch Tuesday" (the second Tuesday of the month) [5][3]. When a new servicing update is released, the preceding update is no longer considered the latest supported level [5][6]. As of May 12, 2026, the latest patch version for the.NET 10 release was 10.0.8 [3]. For the most accurate and up-to-date information regarding specific patch releases or identifying if a newer servicing update has been released since May 2026, please consult the official.NET release notes and the.NET support policy documentation [5][3].

Citations:

Confirm .NET SDK 10.0.301 exists and is production-supported.

The SDK package for 10.0.301 is available (HTTP 200) and it appears in the .NET 10 release metadata; it’s part of the .NET 10.0.9 release (June 9, 2026). Since .NET 10 is LTS-supported through Nov 14, 2028, pinning 10.0.301 should be safe for production, but it’s very recent—cross-check the .NET 10 known-issues list for 10.0.3xx items that may affect CI (e.g., CA1825 false positives around the 10.0.300/3xx range, which can impact builds using TreatWarningsAsErrors).

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@global.json` at line 4, The pinned SDK version "10.0.301" in global.json
should be verified for availability and production support: confirm the SDK
package is downloadable and that 10.0.301 is included in .NET 10 LTS metadata,
then cross-check the .NET 10 known-issues list (look for 10.0.3xx entries such
as CA1825 false positives) to ensure it won’t break CI when
TreatWarningsAsErrors is enabled; if any blocking issues are found, update the
"version" value in global.json to a safer patch (or add CI/workaround notes) and
document the decision in the PR.

},
"test": {
"runner": "Microsoft.Testing.Platform"
Expand Down