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.

Sign up for GitHub

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

Jump to bottom

Version number confusion: 4.2.1 <> 4.2.1alpha0, and its rerelease #235

Open
jengelh opened this issue Feb 10, 2025 · 1 comment
Open

Version number confusion: 4.2.1 <> 4.2.1alpha0, and its rerelease #235

jengelh opened this issue Feb 10, 2025 · 1 comment

Comments

@jengelh
Copy link

jengelh commented Feb 10, 2025

Current release is 4.2.1, but the asset tarball still has alpha0.tar.gz in its name (it was already released like that around Dec 9 2024). How does this fit together?
@musicinmybrain
Copy link
Contributor

I was just about to report this. The problem is that there is a version number hard-coded in Makefile.am, and it wasn’t updated for the release:

givaro/Makefile.am

Line 74 in d288d08

VERSION=4.2.1alpha0

It looks like this value would also affect the version number in the givaro-config script, in the pkg-config file givaro.pc, and in the Doxygen-generated documentation.

@musicinmybrain musicinmybrain mentioned this issue Feb 11, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@musicinmybrain @jengelh