policy on plugin / ormolu versions?

Will HLS be on ormolu 0.5.2.x for a while?
(This is fine with me, I prefer the stability since we use ormolu to standardize our codebase.)
What's the project's policy wrt plugin version bumps?

Actually, do released binaries bundle ormolu 0.5.2.x now? I was assuming from the `flake.lock` that they did, but I don't actually know how that file is used, or whether it's used when releasing HLS binaries.

Thanks

Start by examining flake.lock and the release configuration to determine whether released HLS binaries bundle ormolu 0.5.2.x. Check the existing plugin versioning and release documentation, then document the project's policy and clarify how dependency versions reach released binaries.

Written by the indexing model from the issue text.