Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unlock opam 2.2.0 pre-release #670

Closed
wants to merge 3 commits into from
Closed

Unlock opam 2.2.0 pre-release #670

wants to merge 3 commits into from

Conversation

smorimoto
Copy link
Member

@smorimoto smorimoto commented Jun 29, 2023

I believe there is no real danger in bringing this to the main line because this is needed for #555 and we know that opam pre-releases are reasonably stable 🙂

Signed-off-by: Sora Morimoto <sora@morimoto.io>
@dra27
Copy link
Member

dra27 commented Jun 30, 2023

I think we ought to be cautious having the @v2 tag of setup-ocaml using pre-release opam? (or at the very least, cautious about using an alpha release of opam)?

Signed-off-by: Sora Morimoto <sora@morimoto.io>
@smorimoto
Copy link
Member Author

@dra27 I just added allow-prelease-opam input to select whether to allow to use a pre-release version of opam!

Signed-off-by: Sora Morimoto <sora@morimoto.io>
@smorimoto smorimoto closed this Jul 1, 2023
@smorimoto smorimoto deleted the opam-2.2 branch July 1, 2023 13:09
@zoj613
Copy link

zoj613 commented Aug 22, 2024

@dra27 I just added allow-prelease-opam input to select whether to allow to use a pre-release version of opam!

Is there a way to use a specific version of opam for this github action?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants