Skip to content

Clarify that using global.json may not be rare #44667

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.

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

Merged
merged 2 commits into from
Feb 5, 2025

Conversation

MattKotsenas
Copy link
Member

@MattKotsenas MattKotsenas commented Feb 3, 2025

Summary

Update the word choice for using global.json to select the SDK. The previous word choice made it sound like using a global.json wasn't recommended and reserved for "rare" situations. In practice, many teams want reproducible builds, and as such need to pin developers to a specific version.

To address the concern that global.json can lead to pinning old versions of the SDK, I added a new section calling out that devs can use tools like dotnet sdk check and Dependabot to manage SDK updates.


Internal previews

📄 File 🔗 Preview link
docs/core/versions/selection.md Select the .NET version to use

Update the word choice for using global.json to select the SDK. The previous word choice made it sound like using a global.json wasn't recommended and reserved for "rare" situations. In practice, many teams want reproducible builds, and as such need to pin developers to a specific version.

To address the concern that global.json can lead to pinning old versions of the SDK, I added a new section calling out that devs can use tools like `dotnet sdk check` and Dependabot to manage SDK updates.
@MattKotsenas MattKotsenas requested a review from a team as a code owner February 3, 2025 23:14
@dotnetrepoman dotnetrepoman bot added this to the February 2025 milestone Feb 3, 2025
@dotnet-policy-service dotnet-policy-service bot added dotnet-fundamentals/svc community-contribution Indicates PR is created by someone from the .NET community. labels Feb 3, 2025
@MattKotsenas
Copy link
Member Author

/cc @baronfel for FYI as someone interested in both SDK and reproducible builds

Copy link
Member

@BillWagner BillWagner left a comment

Choose a reason for hiding this comment

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

Thanks @MattKotsenas

This looks great, except for one sentence I found very hard to parse. Check my suggestion, and once that's corrected, this is ready to merge.

Reviewed at commit 1.

Co-authored-by: Bill Wagner <wiwagn@microsoft.com>
Copy link
Member

@BillWagner BillWagner left a comment

Choose a reason for hiding this comment

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

Thanks @MattKotsenas

This LGTM, and I'll :shipit: now.

@BillWagner BillWagner merged commit a10ddc1 into dotnet:main Feb 5, 2025
8 checks passed
@MattKotsenas MattKotsenas deleted the patch-5 branch February 5, 2025 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-contribution Indicates PR is created by someone from the .NET community. dotnet-fundamentals/svc
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants