-
Notifications
You must be signed in to change notification settings - Fork 98
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
Misleading release history among 'Releases' and NuGet #255
Labels
Comments
PS: https://github.com/lduchosal/ipnetwork/releases.atom is for nothing if releases don't end up there... |
Do you have a way to automate github release ? nuget is fully automated. |
Every time I update through NuGet, I feel nervous, I don't know what has changed, I don't know if there is a breaking change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Luc,
https://github.com/lduchosal/ipnetwork/releases suggests the last release of this project was done in 2019. But NuGet reveals a different picture:
Neither is there a change log nor release notes about the many releases since 2019 (also requested by #157 and #251).
And the question is, are this all equivalent final releases? Or are some of them intermediate states of work-in-progress and should not be considered a production-ready release? Only looking at PR history reveals that many releases just are test infrastructure bumps, it even looks like there was no code change the whole 2023. Comparing this to the many NuGet realeases indeed is misleading.
By the way, note that looking at the PR history is only partly helpful, as there is no obvious relation among PRs and version number. Only the date tells which merges ended up in which version.
Proposing to...
Best regards,
Matthias
The text was updated successfully, but these errors were encountered: