Remove pinned OpenSSL packages from Cygwin setup step

[smorimoto]

3.0.16-1 has finally been marked as stable and released, so maybe we can just drop them?
https://cygwin.com/packages/summary/mingw64-x86_64-openssl-src.html

[Copilot]

PR Overview

This pull request updates the OpenSSL version used in the Cygwin setup for OCaml.

• Updated "mingw64-i686-openssl" from version 1.1.1w-0.1 to 3.0.16-1.
• Updated "mingw64-x86_64-openssl" from version 1.1.1w-0.1 to 3.0.16-1.

Reviewed Changes

File	Description
packages/setup-ocaml/src/windows.ts	Updated OpenSSL package versions for Windows setup.

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

[smorimoto]

@MisterDA You might want to try this branch 😉

[dra27]

Why is the =3.0.16-1 necessary?

[MisterDA]

Is it even necessary to always install this package?

[smorimoto]

Why is the =3.0.16-1 necessary?

That was actually what I tried, but the new version was not installed: cfdc9f9
https://github.com/ocaml/setup-ocaml/actions/runs/13776444308/job/38526599501#step:3:50

Is it even necessary to always install this package?

• OpenSSL version in Windows runners #856
• OpenSSL version in Windows runners #856 (comment)

[Copilot]

PR Overview

This PR removes the pinned OpenSSL package versions from the Cygwin setup step to align with the stable release of version 3.0.16-1.

• Removed pinned versions for mingw64-i686-openssl and mingw64-x86_64-openssl.

Reviewed Changes

File	Description
packages/setup-ocaml/src/windows.ts	Removed OpenSSL package pins from the Cygwin setup script.

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

[dra27]

Either the Cygwin cache key needs to be changed (to invalidate Cygwin caches containing the old package) or --upgrade-also needs to be added to the setup invocation. Instinctively I'd invalidate the caches, rather than always running a Cygwin upgrade, but given that the cache key already includes the Cygwin DLL version, maybe always running the upgrade isn't too bad a plan?

Incidentally, rather than scraping cygwin.com for the DLL version (3.5.7), might it be better to parse the table in https://www.cygwin.com/packages/summary/cygwin.html ?

[smorimoto]

I think it makes sense to upgrade every time. Retrieving the DLL version from the table sounds like a fine idea, but I'm worried about which value to retrieve and how frequently it's changed too often.

[dra27]

Retrieving the DLL version from the table sounds like a fine idea, but I'm worried about which value to retrieve and how frequently it's changed too often.

SELECT TOP 1 Version FROM Data WHERE Status = 'stable' ORDER BY SemVer(Version) DESC

That value should change at exactly the same rate as the front page (in theory), because the front page is also supposed to display it!