# \[ANN\] opam-minver 0.2.0 - automatically determine minimum dependency versions **URL:** \ **Category:** Ecosystem\ **Tags:** opam, announce\ **Created:** [July 5, 2026, 11:00pm UTC](https://discuss.ocaml.org/t/ann-opam-minver-0-2-0-automatically-determine-minimum-dependency-versions/18328 "2026-07-05T23:00:37Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![onetimerobot](https://avatars.discourse-cdn.com/v4/letter/o/958977/32.png) [@onetimerobot](https://discuss.ocaml.org/u/onetimerobot)\ **Post date:** [July 5, 2026, 11:00pm UTC](https://discuss.ocaml.org/t/ann-opam-minver-0-2-0-automatically-determine-minimum-dependency-versions/18328/1 "2026-07-05T23:00:37Z")
I have published opam-minver 0.2.0 (previous versions were not released to the public). What it does is use a binary search to find the minimum passing versions of a project’s dependencies listed in its opam file and optionally writes them out to the opam file in-place. I wrote this because I was working on another project (not yet published) and got to the point of listing all the dependencies, and realizing I had no idea what versions it was compatible with. This tool finds that out automatically. It’s pretty well polished at this point, and it has a cmdliner interface, stores its state in a json file so sessions can be resumed if need be, and it also finds the minimum compiler versions and handles split OCaml compiler bounds if, for example, a project doesn’t work specifically with early OCaml 5 versions. This could be used not only for new projects, but also to relax version bounds on any project where they haven’t been determined precisely. Homepage and readme is here: [GitHub - luminous-moose/opam-minver: Automatically determines minimum dependency versions for an opam package. · GitHub](https://github.com/luminous-moose/opam-minver) --- _[View the full topic](https://discuss.ocaml.org/t/ann-opam-minver-0-2-0-automatically-determine-minimum-dependency-versions/18328)._