Mutating `conf-*` packages deps invalidated `opam lock` lockfiles

[yosefAlsuhaibani]

In this commit, a bunch of conf-* packages were mutated to require conf-pkg-config {>= "5"}; this broke lockfiles in e.g https://github.com/semgrep/semgrep/blob/15f510ede866353d84f0193769e854c47e4a0fe9/opam-lockfiles/semgrep.opam.linux-amd64.locked#L63-L73, which at the time the solution was computed it resolved to e.g "conf-zstd" {= "1.3.8"} and "conf-pkg-config" {= "4"}.

Is there another mechanism to do such an update without invalidating existing lockfiles?

[dijkstracula]

Just to add a bit more context: this change has in effect broken all internal CI, blocking builds and releases.

[yosefAlsuhaibani]

Also related: it seem like this has made our windows builds fail to find a solution to installing a list of dependencies that previously had a solution; I've reproduced in this repo https://github.com/yosefAlsuhaibani/opam-windows-repro, where the error we observe is https://github.com/yosefAlsuhaibani/opam-windows-repro/actions/runs/26901884751/job/79356173823

[mseri]

Ping @djs55