(Original) v2.5 release issues / release creation CI issues

[hartwork]

Hi @henry2cox,

when trying to bump lcov to 2.5. for/in Gentoo, I noticed that the 2.5 release is breaking with a few traditions that seem like accidents to me:

• 2.4 had an artifact "lcov-2.4.tar.gz" but there is no "lcov-2.5.tar.gz" with 2.5. Should I be using the git-archive tarball that GitHub offers automatically, in packaging?
• The RPM artifact filename pattern changed from lcov-*-0.(noarch|src).rpm in 2.4 to lcov-*-beta.(noarch|src).rpm in 2.5 without that "beta" being expected or explained on the release page.
• The title is "Release v2.5" for 2.5 when it was plain "v2.4" for 2.4, can be seen at https://github.com/linux-test-project/lcov/releases .

I believe all of the unintended parts could be fixed without need for a new release. Is any of that intended?

PS: Is the "2.4.1" at…

lcov/rpm/lcov.spec

Line 3 in 30056de

Version: 2.4.1

…a leftover? Is that file used in RPM artifact creation?

Best, Sebastian

[henry2cox]

Yes...unintended.
I was hoping/expecting to use the automated rules to build the release without me having to do anything specific on my machine or to upload anything. Seems not to have worked completely.
(Maybe not too surprising, as this is the first time to try it - and there is no way to test without actually building the release.)

I think we can fix whatever we want to fix and then simply overwrite/retag. As far as I can see, there have been exactly 2 downloads :-)

[hartwork]

@henry2cox thanks for your reply! So the "Release " is coming from…

lcov/.github/workflows/rpm_action.yml

Line 53 in 30056de

name: Release ${{ steps.get_version.outputs.VERSION }}

…, I see. So that workflow would also need to create and upload the main .tar.gz source tarball — EDIT see #491 please.

[hartwork]

[..] there is no way to test without actually building the release.

@henry2cox I made #494 now to help with that.

[hartwork]

@henry2cox I'll close this as fixed, please re-open as needed 🙏