Release 0.7.0

[0.7.0] 2025-06-11

Added

• Custom objects enables mapping to custom objects.

• Custom links enables mapping of custom links.

• Fallbacks for required fields enables setting fallbacks for required DevRev fields that are optional in external systems.

Changed

We consolidated all the documentation needed to develop Airdrop snap-ins in our developer documentation.

Feel free to go in-depth about the new features there.

Release 0.6.4

[0.6.5] 2025-05-07

Fixed

Updates the initial-mapping check command to permit transformation methods and devrev fields added on the backend since the last release.

Changed

Backward compatible change to how exported intiial domain mappings are encoded.

Release 0.6.3

[0.6.3] 2025-04-09

Added

This release adds the Authorization policy object that enables mapping of MFZ permissions.

See the developer documentation details.

Release 0.6.2

[0.6.2] 2025-04-08

Fixed

The usage of custom stages in the mcp initial-mapping subcommand.

Release 0.6.1

[0.6.1] 2025-04-07

Fixed

A panic in the new mcp initial-mapping subcommand.

Release 0.6.0

[0.6.0] 2025-04-07

Added

• Added mcp subcommands for launching the chef-cli as an MCP server for use with Cursor, Claude Code and other AI tools which implement an MCP server.

• Added initial-mapping check, which tests a local initial domain mapping file against a local metadata file, simulating how it would behave in an import.

Changed

• The rarely needed install-mapping and convert-mapping subcommands are renamed initial-mapping install ąnd initial-mapping convert

Chef CLI 0.5.6

This release adds support for the platform groups object, allowing mapping to the default rev users and dev users groups in DevRev.

Chef CLI 0.5.5

This release fixes a bug where running initial domain mapping UI would crash for some people. It also lays the groundwork to support new transformation methods and objects in the future.

Chef CLI 0.5.4: documentation

This release fixes a bug where some characters couldn't be used as external field references. It also revamps the chef-cli documentation to make it easier to navigate and to explain why some mappings might be unavailable.
Take a look at the new documentation in the README.

Chef CLI 0.5.3

This release adds the capability to configure custom fields to be constructed in beyond those that are created one-on-one with the external fields coming from the metadata.

It also tightens validations of the metadata:

• it is not permitted to have an enum with no allowed values at all
• it is not permitted to have a reference field without specifying what it refers to.