Bump pubgrub version. #42
Conversation
This bump introduces some minor, backwards incompatible changes to the public API. This is mostly because we expose parts of the pubgrub API that now has been pretty majorly overhauled.
|
I would like a confirmation that pre-releases are handled correctly: basically, they are prioritized last. Any non-pre-release version is chosen before a pre-release. Is this correct, or should a pre-release version only be picked when referenced explicitly? |
|
Hey hey! Thank you for this. Have you got a branch for gleam-lang/gleam with this new version? We'll need to be sure everything works there before we can commit to releasing these changes. I think @giacomocavalieri looked into this also, so I'd like his feedback.
That's right 👍 |
@lpil This is underway and is why I changed the status of this PR to draft. As I worked with integrating this with gleam, I discovered that gleam does not rely on this package for resolution. To not make this package and gleam drift in features, I am leaning on scrapping package-resolution from this package. I will update this when I am done with the gleam-lang integration -- hopefully later this evening. |
|
superseded by #43 |
2 participants
This bump changes the packages public API. This is mostly due to the implementation beeing a bit leaky. If you are unhappy with the changes, I can prioritize stability over ease of implementation. The major changes are mostly due to the change in the
pubgrub::DependencyProvidertrait that got overhauled pretty majorly.