Set an upper bound of dream-httpaf for dream.1.0.0~alpha5-7 #28277
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 sets upper bounds for
dream-httpafindream.1.0.0~alpha5-7as using
dream-httpaf.1.0.0~alpha4causes a compilation failure.We've previously set lower bounds for it in #27034.
This was spotted in #28267
https://opam.ci.ocaml.org/github/ocaml/opam-repository/commit/d0ec749105986928c2134f9046e9b9382af0aafe
causing
To clear up numbering:
dream-httpaf.1.0.0~alpha4was released withdream.1.0.0~alpha8in 0750dde.The opam file for
dream-httpafexplicitly says"This package does not have a stable API."and the release https://github.com/aantron/dream/releases/tag/1.0.0-alpha8 mentionsReplace vendored http/af stack with depending on httpun from opamHopefully this will eliminate a few more CI red lights... 🤞