Support opam 2.6 and default to the HTTP repository - #1132
Merged
Merged
Conversation
Merged
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
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.
The stable version constraint currently excludes opam 2.6.0 even though it has been released. Raise the upper bound to
<2.7.0so ordinary runs can select stable 2.6 releases, and regenerate the distributed bundle.Change the default repository to
https://opam.ocaml.organd update the README. This enables opam 2.6's archive storage optimisation for HTTP repositories; the previous Git default does not benefit from it. The existing cache key includes both the opam version and repository URLs, so this change selects a separate cache entry.Validation:
opam treeJSON schema.Cross-platform integration coverage will come from the existing CI workflow. Setup-time improvements have not been benchmarked.