Programming

17424 readers

48 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Question: Does the build number always increment no matter the version or does the build number resets to 1 for every new version? (programming.dev)

submitted 4 months ago* (last edited 4 months ago) by MortySmith@programming.dev to c/programming@programming.dev

20 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] copygirl@lemmy.blahaj.zone 8 points 4 months ago* (last edited 4 months ago)

Something else to consider in place of or in addition to a build number could also be using the git commit hash of what you're building. Though I would only use that for non-stable releases.

For example, stable versions of Zig look like 0.12.1 and then there's in-development releases like 0.13.0-dev.351+64ef45eb0. It uses semantic versioning where the "pre-release" is dev.351, which includes an incrementing build number, and the "build metadata" is 64ef45eb0, the commit hash it was built from. The latter allows a user to quickly look up the exact commit easily and thus know exactly what they're using.