Release v1.4.8 · Zeugwerk/Twinpack

What's Changed

Package parameters support: Packages can now declare and expose parameters. Parameters are visualized in the catalog (read-only in the UI; configurable only for CI/CD, for now), allowing automated pipelines to inspect and supply package parameters during restore and install operations.
"Use latest version" for dependencies: Resolved an inconsistency when a package is tracked without a pinned version (null in config.json). Twinpack now correctly resolves such entries to the latest available version for both the package itself and its transitive dependencies. The catalog view flattens the dependency tree to display wildcard (*) dependencies consistently.

CLI unusable on non-Windows platforms: Twinpack was constructing paths with Windows directory separators, causing the CLI to fail on Linux and macOS. Paths are now built in a platform-independent way.
Latest version not resolved for local NuGet feeds: The "latest version" lookup was broken for local NuGet repositories, preventing proper upgrades (#167).
Version number missing from CLI assemblies: The version number was not being written into the Twinpack CLI assembly metadata.
Incorrect publish-all-symbols binding: Fixed a binding error for the publish-all-symbols option.
Project name used as PLC name: The project name was incorrectly assigned as the PLC name in certain scenarios.
Potential null pointer: Fixed a null reference that could occur in certain package resolution paths.
No empty Twinpack folder: Twinpack no longer creates an empty Twinpack folder in the solution directory when it is not needed.
Tear down Visual Studio in headed mode: When running in headed mode, Visual Studio is now properly torn down on exit, avoiding leftover processes.

Full Changelog: v1.4.4 → v1.4.8