Adapt Windows CI to new opam 2.3 #161
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tahina-pro
commented
Dec 20, 2024
| name: everparse | ||
| path: everparse | ||
| include-hidden-files: true | ||
| test: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adapts Windows CI to the new official Windows support for OCaml with opam 2.3.
For now this PR assumes a CI machine already configured with
windows-init.ps1introduced by project-everest/everest#118. In other words, this PR does not adaptsrc/package/windows/to the new official opam 2.3; there is no unattended machine configuration yet.However, this PR now tests the EverParse binary package on a GitHub-hosted runner, to make sure the package can work on a bare Windows machine without Cygwin, OCaml, etc.