HFK Release Notes

HFK 5.3.0

Features

Dependencies

  • Update to latest tooling-core 7.4.0

HFK 5.2.0

Bug Fixes

Templates

  • Remove unused function prototype from generated Deploy.h

  • Fix generation failure for required "optional" pub-sub services

Features

Dependencies

  • Update to latest tooling-core 7.3.0

HFK 5.1.0

Bug Fixes

Templates

  • Update component source files to auto-wrap text at 80 characters in header comment text

  • Fix generated channel IDs when connecting a single consumer channel to a multi-channel provider

Features

Dependencies

  • Update to latest tooling-core 6.3.0

HFK 5.0.0

Bug Fixes

Templates

  • Correct behaviour of publishers when no broker is connected

Features

gen-one-c

  • Update Util_Log API to allow printing non-string literal string templates

hfk

  • Include model schemas with released artifacts

Dependencies

  • Update to latest tooling-core 6.2.1

HFK 4.1.2

Bug Fixes

Dependencies

  • Update to latest tooling-core 6.0.3

    • Addresses bugs in validation of tasks in deployment types

Model Service Objects

  • Update hfk to use restructured model service objects

Templates

  • Remove unused files

HFK 4.1.1

Bug Fixes

Dependencies

  • Update tooling-core and model dependencies

Scripts

  • Fix and simplify setup-path.sh

Templates

  • Fix incorrect code generated for multi-channel service connections

  • Fix issues around parameter aliases

  • Fix incorrect parameter block accessor function implementations

  • Fix Deploy_events.h header generated for deployment type events

Testing

behave tests

  • Remove unused test workspaces

HFK 4.1.0

Bug Fixes

Dependencies

  • Remove unused dependencies

Features

Dependencies

  • Update tooling-core to 2.0.1

  • Add gen-one-c in-tree and remove gen-one-c submodule

Testing

Component Types

  • Improve coverage of code generation for persistent configuration

HFK 4.0.5

Bug Fixes

Dependencies

  • Use gen-one-c 3.2.1 in hfk

HFK 4.0.4

Bug Fixes

Templates

  • Fix minor issues with parameter blocks and aliases

HFK 4.0.3

Bug Fixes

Validation

  • Introduce new model validation

    • Ensure instantiated component types in a deployment type have distinct short names

Features

Dependencies

  • Use tooling-core 2.0.0

    • Includes fixes to documentation generation

  • Use gen-one-c 3.2.0

HFK 4.0.2

Bug Fixes

Dependencies

  • Use tooling-core 1.1.3

    • Fixes incorrect channel number usage in service connections

HFK 4.0.1

Overview

The hfk repository contains projects ported from the previous tooling repository, including:

  • bundles

  • common

  • common.templates

  • componentType

  • flightkit

  • legacy-scdb-generator

  • mission

  • mission-databases

  • model-documentation-generators-c

  • module

  • service

  • target

  • workspace

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 ComponentGroup nodes

  • Component grouping is now expressed via dot-separated component names

  • ServiceObject is renamed to ServiceObjectRelation

  • Extends must 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.