Based on the discussion in https://discuss.ocaml.org/t/dropping-some-intermediate-ocaml-versions-from-ci/ I ran the archive-opam tool with the ocaml-lower-bound set to 4.11.0. As a result, the following packages would be archived: Summary (429 unique packages, 1131 total opam files): General: 0.…

Moving forward, I opened the respective PRs: OCaml lower bound is 4.11.0 by hannesm · Pull Request #35 · ocaml/opam-repository-archive · GitHub Archive below 411 by hannesm · Pull Request #29848 · ocaml/opam-repository · GitHub

If you know that you have users on <4.11 then you might decide keep support but you’ll have to rely on other mechanisms than the opam-repo CI for testing. E.g., you might tell your users that you’ll fix the bugs they find but warn them that there’s less testing upstream of their install. Or you migh…

I don’t know exactly where, but maybe we should have somewhere on ocaml.org (/cc @sabine @cuihtlauac ) some documentation in the form: How to install old OCaml compilers (< 4.11) that are no longer maintained in the opam-repository? You must have opam installed. With the command: opam switch create…

For people interested in statistics, there was: 33033 opam packages before archival phase 1 (2025-01-01) 29039 opam packages before archival phase 2 (2025-02-01) 23306 opam packages before archival phase 3 (2025-06-01) 18916 opam packages before archival ocaml lower bound 411 (2026-05-05) 17794 op…

Question: how can the minimum supported OCaml version for opam-repository be lower than the minimum supported OCaml version? According to the OCaml project readme , the currently supported versions are: 4.14 5.3 5.4 5.5

Simply because 4.11 is currently the oldest version of OCaml distributed in the wild. If you’re trying to deploy on real production type machines, it’s best if your dev environment is able to get to the same version or use the system compiler of that distribution. Removing that version would also me…

But distributions are often wildly out of date with OCaml. 4.11.0 was released 6 years ago–surely people can’t be seriously deploying to production with this version. This is why opam manages the compiler version for you as well–you can easily install the latest (or a recent) compiler version and us…

[image] kit-ty-kate: If you’re trying to deploy on real production type machines, it’s best if your dev environment is able to get to the same version or use the system compiler of that distribution. At least on the systems I deploy to, namely debian stable, this is totally unrealistic. I see…

[image] kit-ty-kate: deploy on real production type machines I’m not sure about others, but when I deploy to production, I deploy to machines where there’s no compiler installed… so I package binaries and deploy those. I’m still fine to have 4.11 supported in opam-repository for the means of…

This is closed door for NetBSD entirely.

[archival] [ann] Raising the OCaml lower bound to 4.11.0 for opam-repository

Ecosystem

yawaramin May 7, 2026, 5:15pm 28

The issue is that this lower bound is being used as a justification to force opam package maintainers to support those lower bounds: [ANN] Dune 3.23.0 - #2 by kit-ty-kate

Topic		Replies	Views
Opam repository archival, phase 2 - OCaml 4.08 is the lower bound Ecosystem announce , opam-repository	21	1001	February 26, 2025
Opam repository archival, phase 3 Ecosystem announce , opam-repository	21	1081	December 10, 2025
Opam repository archival, Phase 1: unavailable packages Ecosystem announce , opam-repository	6	606	January 1, 2025
Opam repository archival, next run (scheduled 2026-01-01) Ecosystem opam-repository	9	419	April 8, 2026
Serious OPAM package quality issues Community opam , user-feedback	58	7541	September 25, 2017

[archival] [ann] Raising the OCaml lower bound to 4.11.0 for opam-repository

Related topics