The Progress Chef platform helps teams deliver applications consistently across environments by packaging everything an app needs to run; dependencies, configuration and lifecycle management, all into a single, repeatable unit.
At the core of this approach is Chef Habitat, the application delivery engine that abstracts away environmental differences while preserving operational control. With the general availability of Chef Habitat 2.0, the Chef team introduces important updates that modernize the platform, expand infrastructure support and simplify the overall Habitat experience for today’s environments.
This release brings updates to platform support, modernizes key dependencies and simplifies parts of the Habitat experience. For teams managing applications across different environments, these changes make it easier to run Habitat on modern infrastructure while maintaining consistency and reducing operational overhead.
What Are the Changes in Habitat 2.0 – At a Glance
Chef Habitat 2.0 introduces updates across platform support, performance and CLI behavior. Key highlights include:
- Support for Linux ARM (aarch64)
- Upgrade to PowerShell 7.5.4
- Improved CLI configuration, allowing refresh channels to be set in cli.toml or through hab cli setup
- Improved package uninstall behavior for handling dependency removal
- Removal of several deprecated features and command aliases
The sections below provide more context on these updates and how they improve the Habitat experience.
1. Support for Linux ARM (aarch64)
Chef Habitat 2.0 adds support for Linux ARM architecture (aarch64).
As ARM-based systems become more common in modern infrastructure, this update makes it easier to deploy and manage Habitat workloads across a wider range of environments.
2. PowerShell Upgrade
Chef Habitat 2.0 upgrades the bundled PowerShell version to 7.5.4.
This update introduces performance improvements, including reduced memory (RAM) consumption. Lower memory usage can improve efficiency, particularly in environments where PowerShell is part of build or runtime workflows.
3. Dependency and Security Updates
This release updates several downstream dependencies. These updates address known security vulnerabilities and replace components that were no longer actively maintained.
Keeping dependencies up to date helps support Habitat runs on supported, secure and actively maintained components.
4. CLI Configuration Improvements
Habitat 2.0 introduces additional flexibility when configuring the CLI refresh channel.
The refresh channel determines where the Habitat CLI checks for package updates. It can now be configured either:
- directly in the cli.toml configuration file or
- through the hab cli setup command.
This makes it easier to manage how packages are refreshed across different environments.
5. Improved Package Uninstall Behavior
The hab pkg uninstall command has been updated to improve dependency handling.
Packages can now be uninstalled even when reverse dependencies exist, as long as those dependencies are included in the deletion tree. This allows packages and their dependent components to be removed together when appropriate, simplifying package management.
6. Platform and Feature Cleanup
Chef Habitat 2.0 removes several deprecated capabilities that had been maintained in earlier releases. These changes help streamline the platform by removing legacy functionality that is no longer actively used.
a. Kernel Support
Support for the Linux 2 kernel has been removed. This change aligns Habitat with modern Linux environments and removes support for legacy systems that are no longer widely used.
b. Exporters Removed
Support for the following exporters has been removed, as these platforms are no longer actively maintained within the Habitat ecosystem:
- Mesos exporter
- Cloud Foundry exporter
c. Habitat Package Origin Changes
The Habitat CLI, Supervisor and related component packages have moved from the core origin to the chef origin. This change helps standardize package ownership and simplifies how Habitat components are managed and distributed.
7. CLI Command Changes
Several deprecated CLI command aliases have been removed to simplify the command interface. The following commands should now be used directly:
| Deprecated alias | Use instead |
| Deprecated alias | Use instead |
|---|---|
| hab install | hab pkg install |
| hab run | hab sup run |
| hab apply | hab config apply |
| hab start | hab svc start |
| hab stop | hab svc stop |
| hab term | hab sup term |
| hab setup | hab cli setup |
| hab sup status | hab svc status |
8. Template and Hook Changes
The Handlebars implementation has been updated, which may introduce breaking changes in existing Habitat template files. Users should review the Habitat upgrade guide for details.
In addition, several previously deprecated hook behaviors have been removed:
- Hook file names must now use dashes (-) instead of underscores (_)
(for example, post-run instead of post_run) - The reloadhook has been removed
Users should use the reconfigurehook instead
9. Changes in Configuration Path
The previously deprecated configuration path:
/hab/svc/<service_name>/user.toml
has been removed.
The supported path is now:
/hab/user/<service_name>/config/user.toml
10. Container Export Command Changes
The deprecated command:
hab pkg export docker
has been removed.
Users should now use:
hab pkg export container
This command uses an updated Docker CLI. If the Docker API version used by the CLI is incompatible with the Docker engine in your environment, you may need to set the DOCKER_API_VERSION environment variable to a compatible version (for example, 1.41).
11. Windows Docker Studio Requirements
Entering an interactive Windows Docker Studio using:
hab studio enter -D
is supported only on hosts capable of running a Windows Server 2025 container image. Supported environments include:
- Windows 11
- Windows Server 2025
- Windows Server 2022 running in Hyper-V mode
Upgrade Considerations
Because Habitat 2.0 removes several deprecated features and command aliases, users upgrading from earlier versions should review the following changes before upgrading:
- Removal of deprecated CLI command aliases
- Removal of Mesos and Cloud Foundry exporters
- Removal of Linux 2 kernel support
- Updated configuration path for user.toml
- Updated Handlebars implementation for templates
- Removal of deprecated hook behaviors
Reviewing these changes ahead of time can support the existing Habitat plans and workflows continue to function as expected after upgrading.
Chef Habitat 2.0 continues to build on the core principles of consistency and portability, while simplifying the platform and aligning it with modern infrastructure needs.
Chef Habitat 2.0 reflects a continued focus on simplifying application delivery while keeping pace with modern infrastructure needs. By expanding platform support, modernizing dependencies and removing legacy features, this release makes it easier for teams to package, deploy and manage applications consistently across environments. Whether you’re upgrading from an earlier version or adopting Habitat for the first time, Habitat 2.0 provides a more streamlined, secure and future‑ready foundation for application delivery with the Chef platform.
To learn more about the updates introduced in this release, including detailed upgrade guidance and documentation, please read the documentation listed below. If you are upgrading from an earlier version of Habitat, please review the release notes and upgrade guidance that can help you with a smooth transition.