Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release information not in github #27

Open
toppk opened this issue Aug 25, 2023 · 0 comments
Open

release information not in github #27

toppk opened this issue Aug 25, 2023 · 0 comments

Comments

@toppk
Copy link
Contributor

toppk commented Aug 25, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant