Please create a tag for Coq 8.18 in Coq Platform 2023.10

[rtetley]

The Coq team released Coq 8.18.0 on September 7th, 2023. The corresponding Coq Platform release 2023.10 should be released before November 30th, 2023. It can be delayed in case of difficulties until January 15th, 2023, but this should be an exception.

This issue is to inform you that to our (possibly a few days old) best knowledge the latest released version of your project (1.3.2+8.17) does not work with Coq 8.18.0. We tried to remove version restrictions in opam files and possibly make or configure files, but this did not suffice.

Please note that in Coq Platform CI (unlike Coq CI) we test only released / tagged versions. Coq CI appears to test this project, but has some special handling for your project which makes it difficult to retrieve the commit it tests for your project.

Could you please create a tag and opam package, or communicate us any existing tag that works with Coq branch v8.18, preferably before October 31st, 2023? In case we might have to delay the Coq Platform release cause of issues with your project, we would prefer to be informed about the situation as early as possible.

In case the tag and opam package are available before October 31st, 2023, it will be included in an early Coq Platform beta release of the for Coq 8.18.0.

The working branch of Coq Platform, can be found here main. It contains package pick ~8.18+beta1 which already supports Coq version 8.18.0 and contains already working (possibly patched / commit pinned) Coq Platform packages.

Please don't close this issue, even after creating the new tag and/or opam package. We will close the issue after updating Coq Platform. This is a measure of 'double book keeping' in order to avoid that we ship the wrong version.

In any case, Coq Platform won't be released before this issue is closed!

Thanks!

P.S.: this issue has been created automatically based on CI status.

CC: https://github.com/coq/platform/issues/372

[rtetley]

Hey @lukaszcz, doing a round of reminders :-) Could you give us a status update ?

[lukaszcz]

Ah, sorry, I've been a bit busy recently. I'll definitely create a release for Coq 8.18 by the end of this week.

On Tue, 31 Oct 2023, 15:36 Romain Tetley, @.***> wrote:

Hey @lukaszcz https://github.com/lukaszcz, doing a round of reminders :-) Could you give us a status update ?

— Reply to this email directly, view it on GitHub https://github.com/lukaszcz/coqhammer/issues/165#issuecomment-1787347509, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPKH3FFHI2KF56SW72CZLYCEEG3AVCNFSM6AAAAAA5UGTOASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBXGM2DONJQHE . You are receiving this because you were mentioned.Message ID: @.***>

[palmskog]

@lukaszcz please let us know if you'd like help with the packaging. We can also help with adding GitHub Actions CI if you want (the Travis CI seems to not work anymore).

[lukaszcz]

I created a release for Coq 8.18.

Regarding Travis CI, it tells me "Builds have been temporarily disabled for public repositories due to a negative credit balance." This is strange, because I have plenty credits left.

[MSoegtropIMC]

@lukaszcz : I updated to coq-hammer-tactics.1.3.2+8.18 + coq-hammer.1.3.2+8.18, which works.

Btw.: did you try the 3.0 beta of Eprover? Stephan Schulz told me there will be an official 3.0 release in the next days. With Z3 I will continue to use 4.11.2 - 412.2 has build issues on ARM Macs.

Can you tell me which versions of CVCx and Vampire are supported? I could give it another try then.

[MSoegtropIMC]

@rtetley @lukaszcz : I cannot close this issue. Can you please close it?