[cli] Remove legacy config file migration logic #8199
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
TooTallNate
commented
Jul 21, 2022
| '// Note': | ||
| 'This is your Vercel config file. For more information see the global configuration documentation: https://vercel.com/docs/configuration#global', | ||
| '// Docs': | ||
| 'https://vercel.com/docs/project-configuration#global-configuration/config-json', |
There was a problem hiding this comment.
Fixed these docs links too since they pointed to an incorrect page.
styfle
reviewed
Jul 21, 2022
styfle
approved these changes
Jul 21, 2022
…li-legacy-config-migration
styfle
approved these changes
Aug 3, 2022
|
Though this is technically a breaking change, we decided to merge as a "patch" change since the logic is so legacy that anyone who needed to migrate should have at this point. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Removes the legacy config file migration logic from back in the days when Zeit CLI supported multiple "providers". This was from a very long time ago and we should expect that anyone who would have migrated at this point, has.