Release version number shown on GitHub is not latest release, leading to confusion

[mhucka]

restview is excellent! One thing that confused me, however, is that on GitHub the latest version on the releases page is 2.0.4, which is actually not the latest version that one gets from pip install restview.

Given that PyPI seems to be the location where releases are actually put, perhaps it would be best to simply remove the releases from GitHub. Alternatively, it might help to have a note somewhere to explain that people should ignore what they see on the releases page because it doesn't reflect the real latest release.

[stevepiercy]

@mgedmin would you please cut all unreleased releases on GitHub? GitHub can generate release notes from tags.

[mgedmin]

Apologies, I keep forgetting to update GitHub releases when I use my release automation via make release. I'll update the Makefile to print a reminder.

(I'm used to considering https://pypi.org/project/restview/#history as the canonical place that lists all releases.)

[mgedmin]

The annoying part about adding GitHub release notes after the fact is that GitHub then decides the release was made today. This makes me reluctant to add missing GitHub releases for older tags.

Is there a way around this?

[stevepiercy]

Is there a way around this?

Not that I could find. https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases

[mhucka]

I haven't tried it myself, but this sounds like a method to do that:

https://gist.github.com/frederikheld/191844766e82f669da26dac26e23ef8e

There's also this discussion on Stack Overflow: https://stackoverflow.com/q/21738647/28972686 – in particular the answer https://stackoverflow.com/a/76784008/28972686 seems to be a solution, if I'm reading it correctly.