Jean-Sébastien Pédron

> In the future when we want to unregister projections, we can add that step before `rabbit_khepri:register_projections/0` to the enable callback for the `khepri_db` feature flag (using [rabbitmq/khepri#282](https://github.com/rabbitmq/khepri/pull/282)). Do you...

Khepri 0.15.0 is now released and used in RabbitMQ `main` branch.

@dcorbacho: Do you have a link to a failing CI job or node logs?

RabbitMQ does not use semantic versioning for its own components currently. As @michaelklishin said, the `rabbit_common` version pinning in `amqp_client` is strict for this reason. About the pinning of third-party...

Note that Erlang.mk, the build tool we use, does not have a "lock" mechanism like other build tools, so we can't rely on such a thing.

> If you use another build tool that does not support lock files I suggest changing the package metadata before publishing or listing project dependencies and package dependencies separately. I...

> It seems like all the packages you publish support building with both Erlang.mk and rebar3, at least that's what is in the package metadata. Hmm, you're right, I was...

I believe it has been fixed by #12853 which handles the possible timeout from Khepri and retries. This was worked on as part of a failure in CI and it...

Yeah, I think these are the same issue. I will mark it as resolved and we can reopen it if we discover they are different. Fixed by #12853.

Raft ticks and hearbeat RPCs are there for this reason. There must be a code path in Ra where the tick timeout is not emitted or has no effects.