Releases: golf1052/code-sync
CodeSync 2.7.3
Added
- Added a CHANGELOG.md
- Added a CONTRIBUTING.md
Removed
- Removed support for VSCode 1.13 making the minimum required VSCode version 1.14 because the minimum
@types/vscodeversion is 1.14. This is a minor version bump because VSCode 1.13 is over 3 years old now so nobody should be using that version.
Fixed
- Upgraded dependencies
CodeSync 2.7.2
Fixed
- Fix Linux VSCode non Snap package bug
CodeSync 2.7.1
Fixed
- Bug where extension would not load in some cases due to not being able to find
settings.json - Bug where extensions would not export correctly
CodeSync 2.7.0
Added
If you use a non standard install of VSCode you can now set the name of the VSCode executable or the VSCode user settings path that CodeSync will use. The new commands added are CodeSync: Set VSCode executable name and CodeSync: Set VSCode settings path. See #41. Thanks to @convexshiba for this feature request.
CodeSync 2.6.2
Fixed
- Code not found on path errors when VSCode was installed through Snap on Linux. See #38
CodeSync 2.6.1
Fixed
- CodeSync will not migrate your settings files from a previous version of CodeSync if your current CodeSync version already has settings files. This means that any new settings will not be overwritten by your previous version's settings.
- The status bar will now be correctly reset if CodeSync could not find VSCode's settings file when trying to export settings.
- Added more logging when exporting settings.
CodeSync 2.6.0
Updated chokidar to version 3 which should provide performance improvements.
CodeSync 2.5.3
Export extensions after import has completed. Rarely, CodeSync would not be able to export extensions before the extension was deactivated so this guarantees the list of installed extensions gets saved at least once.
CodeSync 2.5.2
Only tries to install extensions that are not reported as being installed when importing extensions. Fixes #30. Thanks to @wesmdemos for the report.