The upcoming holoscan-cli v4.3 release intentionally drops the Holoscan Application Package (HAP) / MONAI Application Package (MAP) application packaging workflow that previous releases exposed via:
holoscan package
holoscan run (HAP)
holoscan nics
- the
monai-deploy console script
The CLI is being consolidated around the HoloHub-style source-project lifecycle (build / run / test / install / lint / container / info commands). HAP / MAP container packaging is out of scope for that surface and the implementation is being removed rather than carried forward.
What this means
- Anyone running those commands from a current install will continue to work until v4.3 ships.
- In v4.2, typing any of those names prints a removal note pointing back at this issue and exits 2.
Workarounds
- Pin
holoscan-cli<=4.2.0 — the last release that shipped the HAP / MAP interface.
- Or use the Holoscan SDK packaging workflows directly (see the Holoscan SDK User Guide).
Tracking
This issue is the public deprecation notice referenced from the README's "Deprecations" section. Please subscribe here for the v4.3 release date and any change in scope.
The upcoming
holoscan-cliv4.3 release intentionally drops the Holoscan Application Package (HAP) / MONAI Application Package (MAP) application packaging workflow that previous releases exposed via:holoscan packageholoscan run(HAP)holoscan nicsmonai-deployconsole scriptThe CLI is being consolidated around the HoloHub-style source-project lifecycle (build / run / test / install / lint / container / info commands). HAP / MAP container packaging is out of scope for that surface and the implementation is being removed rather than carried forward.
What this means
Workarounds
holoscan-cli<=4.2.0— the last release that shipped the HAP / MAP interface.Tracking
This issue is the public deprecation notice referenced from the README's "Deprecations" section. Please subscribe here for the v4.3 release date and any change in scope.