fix(docs): Correct default rollForward policy in global.json documentation #44996
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📜 Description
This PR updates the global-json.md documentation to correctly reflect the default
rollForward
behavior in the .NET SDK.🔍 Issue
The documentation previously stated:
However, based on actual SDK behavior and tracing logs (see dotnet/core-setup#6953), the default policy is actually
patch
, notlatestPatch
.🛠 Fix
global-json.md
to specifypatch
as the default rollForward policy.📎 Related Issues
📸 Verification
✅ The demo provided in the issue confirms that
patch
is the default policy.✅ Tracing logs explicitly state
rollForward = 'patch'
.📂 Files Changed
docs/core/tools/global-json.md
🔗 Additional Context
For backwards compatibility, the SDK defaults to
patch
whenrollForward
is not specified inglobal.json
. This update ensures that the documentation accurately reflects this behavior.Internal previews