Skip to content

[Repo Assist] eng: add global.json to pin .NET SDK to 10.0.x #123

@github-actions

Description

@github-actions

🤖 This is an automated pull request from Repo Assist.

Summary

Adds a global.json at the repository root to pin the .NET SDK to 10.0.x.

Problem

Without a global.json, any .NET SDK version installed on the machine is used. This creates two risks:

  1. Version drift between machines — a developer on SDK 10.0.200 and CI on 10.0.102 may see different compiler diagnostics or NuGet resolution.
  2. Accidental forward jumps — once .NET 11 SDKs are installed, builds silently switch to .NET 11 without anyone noticing.

Fix

{
  "sdk": {
    "version": "10.0.102",
    "rollForward": "latestFeature"
  }
}

rollForward: latestFeature means:

  • ✅ Patch updates (10.0.103, 10.0.200) are accepted automatically
  • ✅ Feature bands within .NET 10 (10.0.200, 10.0.300) are accepted
  • ❌ A jump to .NET 11 requires an explicit update — intentional breakage prevention

Tracking

This resolves the proposals in issues #106 and #116, which were filed when the automated PR creation was blocked by the repository's protected-files policy for global.json.

Test Status

✅ All 503 shared tests pass, 18 skipped (Windows-only infrastructure): dotnet test tests/OpenClaw.Shared.Tests/
✅ All 93 tray tests pass: dotnet test tests/OpenClaw.Tray.Tests/
✅ CI already uses dotnet-version: 10.0.x — no workflow changes required

Generated by Repo Assist ·

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@cbb46ab386962aa371045839fc9998ee4e97ca64

Warning

🛡️ Protected Files

This was originally intended as a pull request, but the patch modifies protected files: global.json.

These files may affect project dependencies, CI/CD pipelines, or agent behaviour. Please review the changes carefully before creating the pull request.

Click here to create the pull request once you have reviewed the changes

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions