You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the 0.9.3 isn't taged in github, and theres no 0.9.3 release on gh, and even the 0.9.3 pyproject isn't on github, I had to download the 0.8.19 sources and 0.9.3 sources to see what changed.
I routinely examine updates in particular when there are minor or major bumps to understand if I have to adopt to a new best practice or incompatible change.
also, while i agree this change warrants a minor bump, given the exceptions are being rearranged, I don't understand why jumping to 0.9.3 instead of 0.9.0. I'll assume there's some internal activity that isn't in the git commit logs (clearly), but I recommend using semver prelease for such things, so that there's some semblance of order to outsiders.
as for the changelog/release notes this would be valuable, and I know there's tools like town crier but I don't think it's necessarily easy to adopt.
Since the 0.9.3 isn't taged in github, and theres no 0.9.3 release on gh, and even the 0.9.3 pyproject isn't on github, I had to download the 0.8.19 sources and 0.9.3 sources to see what changed.
I routinely examine updates in particular when there are minor or major bumps to understand if I have to adopt to a new best practice or incompatible change.
also, while i agree this change warrants a minor bump, given the exceptions are being rearranged, I don't understand why jumping to 0.9.3 instead of 0.9.0. I'll assume there's some internal activity that isn't in the git commit logs (clearly), but I recommend using semver prelease for such things, so that there's some semblance of order to outsiders.
as for the changelog/release notes this would be valuable, and I know there's tools like town crier but I don't think it's necessarily easy to adopt.
here's a shout out to msgspec, which I think has really nice release notes. https://github.com/jcrist/msgspec/releases
The text was updated successfully, but these errors were encountered: