This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Add sdk roll.forward policy in global.json #39428
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wtgodbe
approved these changes
Jul 12, 2019
|
Merging as that setting is ignored with the current SDK. Unblocking local devs that right now install a newer feature band. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I just noticed that the added sdk version forces everyone now to install that sdk version. Newer versions beyond the patch level aren't valid with the default roll-forward policy. Setting to major to not restrict any newer sdk version.
The change was merged two days ago: dotnet/core-setup#6953. Ideally we would also update the sdk but I'm hesitant to force every dev in corefx to download the very latest nightly build.