My package uses a manual packages.json file to specify Windows-only compatability. However I am concerned that now defining packages.json schema 2.0 there will break backwards compatability. If I now use schema 2.0 for packages.json - what will happen to the users who are still using the old version of the package control plugin?
Is it possible to specify both the schema 1.2 and schema 2.0 in packages.json - so that it will work for both old and new users of the package control plugin?