We are delighted to announce the availability of Chef InSpec version 5.24.24!
Deprecations
The --overwrite flag does not work as expected while using the inspec compliance upload command to upload to Automate. This option will be removed going forward. (#7971)
Improvements
- Moved the omnibus build configuration to a private Git submodule to improve control over official release builds. Community contributors can continue building InSpec packages using the public
inspec-omnibus-community-configrepository. (#7827)
Bug fixes
- Fixed resource ID extraction in the JSON reporter to correctly prefer the resource object's ID when available, escape regular expressions, and cap resource IDs at 256 characters to prevent bloated reports. (#7799)
- Fixed an issue where controls waived with
run: falsestill executed the entire control block before skipping, causing expensive commands to run unnecessarily. InSpec now pre-checks waivers before evaluating the control block, so waived controls skip execution entirely. (#7832) - Fixed an issue where the
packageresource failed to detect 32-bit packages when running InSpec against Windows Server 2025 through a WinRM session (for example, with Test Kitchen). PowerShell WinRM sessions don't expand CMD-style environment variables, which caused architecture detection to return an unknown value andWOW6432Noderegistry paths to be skipped, making 32-bit packages appear as not installed. Train now falls back to PowerShell-native syntax for architecture detection when CMD variable expansion fails. (#7935, train #832)
Security fixes
- Updated
addressablegem constraint from< 2.8.8to~> 2.9. (#7920) - Updated
jsongem from>= 1.8to>= 2.19.2. (train #829) - Updated
activesupportgem from>= 7.2.2.1to>= 7.2.3.1. (train #830) - Updated
net-imapgem from>= 0.2.5to>= 0.5.14. (#7924) - Updated
nokogiritest dependency gem from1.17.1to1.18.10. (#7946)
Dependency updates
- Updated train and train-core from 3.16.1 to 3.16.5. (#7925)