Misleading release history among 'Releases' and NuGet

[maettu-this]

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...

• ...add a change log or release notes as requested by #157 and #251.
• ...either remove the https://github.com/lduchosal/ipnetwork/releases and clearly state at https://github.com/lduchosal/ipnetwork that releases solely are to be found in NuGet.
• ...or reactivate GitHub releases for those versions that include functional changes and are considered production-ready.

Best regards, Matthias

[maettu-this]

PS: https://github.com/lduchosal/ipnetwork/releases.atom is for nothing if releases don't end up there...

[lduchosal]

Do you have a way to automate github release ? nuget is fully automated.

[GF-Huang]

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.