CI broken will break with update to 8.20

[Zimmi48]

Our current CI setup always uses the latest version of Coq.

A recent (auto-)upgrade from Coq 8.19 to Coq 8.20 has broken the CI (some tutorials are not compatible).

In practice, it seems not so reasonable to only test the latest Coq version given that the deployment still uses Coq 8.17 through jsCoq.

A natural solution would be to fix the Coq version used for the deployment to the one available in jsCoq and at the same time have other test jobs for different Coq versions.

[thomas-lamiaux]

@Zimmi48 duplicate of #64 ?

Anyway, if we switch to JsCoq2 soon, we will just be using 8.20 ?
We have not discussed the timeline yet, but I think it is fine to target compatibility with Rocq1 for the 1st "release" / index version, and hence to use the latest Coq version.

I'll try later with Coq 8.20 but I found the error weird.

[thomas-lamiaux]

Actually, I would prefer to use the current version of the coq platform because it is less work

[Zimmi48]

@Zimmi48 duplicate of #64 ?

Duplicate of what? This is #64.

compatibility with Rocq1

FTR, the first release of Rocq will be Rocq 9.0.

[thomas-lamiaux]

ha I meant #48.

[thomas-lamiaux]

I am renaming it