You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Releasing? (Docker CI images do not support latest stdlib) #230
When the stdlib split was proposed, IIRC the tentative agreement was to keep release schedule in sync with Rocq until decided otherwise. Yet looks like we completely forgot to figure out and distribute the work of actually keeping it in sync? Now it seems that there is no 9.1 release or 9.2-release candidate, and opam users are still on stdlib 9.0, blocking use of new stdlib features there.
What's to do? I definitely do not wish for opam-release management duties.
I'll do a release once 9.2+rc1 is out. But if you want to do it feel free to (the release process is documented in dev/doc/howto_release.md and seems relatively simple), I can handle the opam and nix packaging anyway, just let me know so that we don't duplicate work.
I'll let opam packagers move the opam file if they want (for instance along with adding the Rocq 9.2.0 file). Anyway, the current package is enough to build the Docker images so it's not impairing the release process for Rocq 9.2.
Being a bit patient, Docker images have a new maintainer, let him some time to do the job, we are still very early in the release process of Rocq 9.2 so building Docker images for it is the next step there.
Meanwhile, I guess you can still explicitly opam install coq-stdlib.x.y.z for the version of Stdlib you want in the CI scripts (may also need an opam update).
I'll let opam packagers move the opam file if they want (for instance along with adding the Rocq 9.2.0 file).
Who are "the OPAM packagers" who are supposed to do that, so that I can ping them? or submit rocq-stdlib 9.1.0 to the main OPAM repository myself. The current situation, with different versions of rocq-stdlib in different OPAM repositories, is not acceptable. See #256.
This issue is not "completed". Perhaps it should be migrated elsewhere or assigned to somebody else, but out of respect for our users struggles, let's not close it.
changed the title [-]Releasing? (CI infrastructure provided by Rocq does not support latest stdlib)[/-][+]Releasing? (Docker CI provided by Rocq does not support latest stdlib)[/+]on May 17, 2026
changed the title [-]Releasing? (Docker CI provided by Rocq does not support latest stdlib)[/-][+]Releasing? (Docker CI images do not support latest stdlib)[/+]on May 17, 2026
Activity
SkySkimmer commentedon Jan 28, 2026
rocq 9.2 is not compatible with stdlib 9.0 so a release is needed anyway
proux01 commentedon Jan 29, 2026
I'll do a release once 9.2+rc1 is out. But if you want to do it feel free to (the release process is documented in dev/doc/howto_release.md and seems relatively simple), I can handle the opam and nix packaging anyway, just let me know so that we don't duplicate work.
SkySkimmer commentedon Feb 14, 2026
I see the package for stdlib 9.1.0 in https://github.com/rocq-prover/opam but shouldn't it be in https://github.com/ocaml/opam-repository/ (where the package for 9.0.0 is)?
proux01 commentedon Feb 16, 2026
I'll let opam packagers move the opam file if they want (for instance along with adding the Rocq 9.2.0 file). Anyway, the current package is enough to build the Docker images so it's not impairing the release process for Rocq 9.2.
andres-erbsen commentedon Feb 18, 2026
I am failing to use the new release in downstream CI. Is there still something to be done? (.opam diff)
proux01 commentedon Feb 18, 2026
Being a bit patient, Docker images have a new maintainer, let him some time to do the job, we are still very early in the release process of Rocq 9.2 so building Docker images for it is the next step there.
proux01 commentedon Feb 18, 2026
Meanwhile, I guess you can still explicitly
opam install coq-stdlib.x.y.zfor the version of Stdlib you want in the CI scripts (may also need anopam update).andres-erbsen commentedon Apr 3, 2026
This still isn't fixed: https://github.com/thery/coqprime/actions/runs/23934251655/job/69807458543?pr=94
proux01 commentedon Apr 7, 2026
The release has been done, Docker issues should be reported there.
xavierleroy commentedon Apr 16, 2026
Who are "the OPAM packagers" who are supposed to do that, so that I can ping them? or submit rocq-stdlib 9.1.0 to the main OPAM repository myself. The current situation, with different versions of rocq-stdlib in different OPAM repositories, is not acceptable. See #256.
andres-erbsen commentedon May 17, 2026
This issue is not "completed". Perhaps it should be migrated elsewhere or assigned to somebody else, but out of respect for our users struggles, let's not close it.
[-]Releasing?[/-][+]Releasing? (CI infrastructure provided by Rocq does not support latest stdlib)[/+][-]Releasing? (CI infrastructure provided by Rocq does not support latest stdlib)[/-][+]Releasing? (Docker CI provided by Rocq does not support latest stdlib)[/+][-]Releasing? (Docker CI provided by Rocq does not support latest stdlib)[/-][+]Releasing? (Docker CI images do not support latest stdlib)[/+]