HFK Release Notes
HFK 4.0.0
Overview
This release introduces a major update to hfk, including migration to a new tooling-core, MAL, and code generation pipeline. Significant internal and structural changes were required across templates, models, views, and generated artefacts.
Key high-level changes include:
-
Migration to new tooling-core with new MAL and code generation
-
Major restructuring of model entities and templates
-
Introduction of new Views and definition handling
-
Significant changes to Deployment and DeploymentType handling
-
Consolidation of task and execution lists
-
Integration of gen-one-c components
-
Extensive updates to validation, ordering, and dependency resolution
-
Updates to template logic to handle renamed, moved, or reformatted entities
-
Numerous fixes to code ordering, linkage, and generation correctness
-
Updates to behave test suites and reference workspaces
Breaking Changes
Changes that break existing workspaces include:
-
Deployment types can no longer contain
ComponentGroupnodes -
Component grouping is now expressed via dot-separated component names
-
ServiceObjectis renamed toServiceObjectRelation -
Extendsmust appear first in XML definitions -
Service connections now require unique channel identifiers
-
Numerous error messages have been updated or made more specific
-
Boards, OSALs, and architecture compatibility checks are stricter
-
Version validation and dependency resolution have been tightened
These changes may require updates to deployment types, missions, bundles, and workspaces to comply with new validation rules.
Error Message Changes
A large number of error messages were updated, primarily to improve clarity, precision, and consistency. These include changes to:
-
Dependency resolution errors
-
Version validation errors
-
Mission and deployment loading errors
-
Component, service, and route validation errors
-
Architecture compatibility errors
The revised messages provide more detailed diagnostic information and context compared to previous versions.