-
-
Notifications
You must be signed in to change notification settings - Fork 814
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
Update packagecontrol.io For New Schemas #1517
Comments
Is it planned to keep creating channel_v3.json for Package Control 3.4 (for ST2 users) or should database scheme be updated to 4.0.0 as well (drop load_order column)? ST2 users wouldn't have access to default chennel anymore, if no or a dummy channel_v3 (for PC update) is left behind. In short: Completely drop support for ST2 and ST3 before 3143? |
I think we’ll update the schema but not the file name. I believe that old clients will error out. Either way, no use supporting ST2. |
With a look at channels.json, providing a dummy channels_v3 which contains Package Control 4.0 release only might be a more robust solution for smooth transition, IMHO. Just changing scheme version might leave all users behind, which haven't upgraded to PC4.0 before channel_v3 scheme changes upstream. |
Since dependencies need a new python_version field in the JSON schemas, the https://packagecontrol.io code will need to be updated also.
Here are a few relevant places:
There are likely a few more I haven't thought of, off of the top of my head.
The text was updated successfully, but these errors were encountered: