Skip to content

Conversation

@XiuhuaRuan
Copy link
Contributor

The version number remains 2.0.0 while the the release number has upgraded to v2.4.0. We suggest to update the version number along with the release number to avoid version confusion.

@pashagolub
Copy link
Collaborator

Hello.

This variable is automatically set during the release workflow.

But thanks anyway.

@pashagolub pashagolub changed the title update the version number to match the current release v2.4.0 [*] update the version variable default value to match the current release v2.4.0 May 6, 2024
@pashagolub pashagolub self-assigned this May 6, 2024
@pashagolub pashagolub merged commit 20e1391 into cybertec-postgresql:master May 6, 2024
@XiuhuaRuan
Copy link
Contributor Author

@pashagolub It's my pleasure to make a little contribution to the community. Could you please double check if the release workflow is working normally and this variable is automatically set? Seems this variable keeps 2.0.0 in recent several releases.

@pashagolub
Copy link
Collaborator

How did you get the binary? Did you download it from GitHub?

@XiuhuaRuan
Copy link
Contributor Author

Oh,I got it. The binary directly downloaded from GitHub has the correct version number. I built the binary from source so got the legacy version number. Anyway, we should have the updated version number in source code, right?

@pashagolub
Copy link
Collaborator

Yeah, I already merged the PR. Thanks for pointing this out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants