lower-bounds: run the check with the opam-repository-archive on #444
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
shonfeder
approved these changes
Jul 11, 2025
Member
|
Thanks! I'm not 100% convinced that we want to keep testing stuff form the archive long term, but I also don't see any harm in adding this for the moment. |
Currently the opam-repository will test the lower bound on most latest versions of packages. And even though most cases are avoided by the fact that we add upper bounds to all archived packages, the new packages may still be compatible and co-installable. So we should keep checking the lower bounds with the whole database to ensure that the metadata on the opam-repository remains consistent
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently the opam-repository will test the lower bound on most latest versions of packages. And even though most cases are avoided by the fact that we add upper bounds to all archived packages, the new packages may still be compatible and co-installable. So we should keep checking the lower bounds with the whole database to ensure that the metadata on the opam-repository remains consistent.
This will also help to ensure that all the people that use the archive in their CI do not have unpleasant surprises.