Closed clarkevans closed 3 years ago
It would cause a similar release cascade if JSON released 2.0 though, so not sure what you mean.
@fredrikekre This is not just a technical request: it's a process request -- that JSON become stable enough to where future breaking changes are not expected.
Isn't it already?
It's clear we have a fundamental disagreement, and it's your project. Thank you for your consideration.
and it's your project.
Not at all, I don't think I have even contributed to this package.
Registrator is now complaining if you don't really pin down packages.
Hence, I now have
JSON = "0.21"
in my[compat]
which will likely cause a release cascade when JSON bumps to v0.22.