v0.44.6

This release fixes container startup failures on fresh deployments and enables advanced variable types for bridge template configurations.

Fixes

• Containers now start reliably on fresh deployments. Previously, containers could fail to start with "permission denied" errors when services tried to write to temporary directories. This only affected fresh installations without Docker cache - upgrades and cached deployments were not impacted. The issue was caused by a known Docker BuildKit limitation that doesn't preserve directory permissions during multi-stage builds.

Improvements

• Bridge templates now support array and object variables. You can now use complex variable types in your protocol converter YAML configurations, not just simple text values. This enables bulk configuration patterns like defining a list of PLC addresses with their tag names, units, and data contracts as a single variable, then iterating over them in your template with {{ range .AddressMappings }}. This is particularly useful for S7 and OPC UA bridges where you need to map many addresses to tags.

Example usage in YAML:

templateInfo:   isTemplated: true   variables:     - label: "AddressMappings"       value:         - Address: "DB1.DW20"           TagName: "temperature"           Unit: "celsius"         - Address: "DB1.DW24"           TagName: "pressure"           Unit: "bar"

Then in your template: {{ range .AddressMappings }}{{ .Address }} -> {{ .TagName }}{{ end }}