elm/http was upgraded to 2.0 yesterday.
Packages that use this e.g.
dillonkearns/elm-graphql can upgrade their dependency and then publish a minor version.
But if I try to upgrade
elm-graphql all my code that uses Http won’t work. I’m forced to upgrade
elm/http as well and change my code
My understanding of a minor version if that I should be able to bump that library without touching any of my code, which is not true here.
I’m not an expert on semver but this seems off.
Shouldn’t upgrading a major version in a peer dependency require a major version bump in a library?