Installing
honig installs as a pre-built binary with cargo-binstall:
cargo binstall cargo-honig
In CI and in a team, install one version everywhere. Two versions of the generator write different code and a different honig dependency:
cargo binstall cargo-honig@x.y.z
Updating
Install the new generator, then generate again:
cargo binstall cargo-honig
cargo honig generate
generate moves the honig dependency to the version of the generator. The two always match: the generated code calls runtime internals that change between versions.
A bot such as Renovate or Dependabot bumps honig alone, without the generator, so the generated code no longer matches. Turn it off for honig. In renovate.json:
{
"packageRules": [{ "matchPackageNames": ["honig"], "enabled": false }]
}