Platform
Darwin Beast-Machine.local 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64
Sketchpacks for macOS Version:
Version 0.5.7
Steps to reproduce
Install any plugin available in Sketchpacks.
Observe its "lock" status in the Managed view
Current behavior
Sketchpacks seems to default all new plugins to the Full Locked state. This means the plugin will stay at exactly that version and no updates will be applied.
Expected behavior
While major plugin updates could result in broken workflows, I think the argument could be made for defaulting to a lesser lock. There are four available levels: I'd suggest defaulting at least to Patch Updates.
Workaround
The user can of course change the lock state for every managed plugin. It's just a little tedious.
Platform Darwin Beast-Machine.local 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64
Sketchpacks for macOS Version: Version 0.5.7
Steps to reproduce
Install any plugin available in Sketchpacks. Observe its "lock" status in the Managed view
Current behavior
Sketchpacks seems to default all new plugins to the Full Locked state. This means the plugin will stay at exactly that version and no updates will be applied.
Expected behavior
While major plugin updates could result in broken workflows, I think the argument could be made for defaulting to a lesser lock. There are four available levels: I'd suggest defaulting at least to Patch Updates.
Workaround
The user can of course change the lock state for every managed plugin. It's just a little tedious.