Release v0.6.4 · Zeugwerk/Twinpack

What's Changed

TwinpackCli push command can now be used without a config.json file. All mandatory information for publishing is extracted directly from the .library file(s). The config file can still be used for optional meta data.
Introducing Twinpack Registry, which allows to publish packages directly from GitHub releases. To make a package available on Twinpack simply create a PR in this repository, which adds your GitHub project to the repositories.txt file.
Package binaries (.library files) can now be downloaded from arbitrary locations. For instance, directly from a GitHub release. When publishing with Twinpack Registry this is the new default.
Twinpack now stores a hash for every package version. Together with arbitrary download locations, this is used to check if a binary has been tempered with after publishing and the user is warned.
Implemented a Library Reader that can reliably extract meta information from .library files
Improved User experience when searching packages, it is much faster now and packages already fetched are available instantly
Asynchronous operations now all use cancellation tokens so the can be aborted, which can be triggered in the Visual Studio Extension

Fixed a crash of Visual Studio / XAE Shell, which occurs if a function block of a library is displayed and the library simultaneously updated by closing all library related windows before performing an update.
Installing dependencies now is recursively
Installing Runtime Licenses now is recursively
License Dialogs now is recursively
The catalog is now properly locked during updates
The “Load More” button now is only visible in the catalog view
Create config now also works correctly if the config.json only covers some of the PLCs in the project