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.
I believe “copyright free” in this case doesn’t mean not protected by copyright, but rather that it was missing attribution, so they could not contact the original creator.
Anything you create is automatically protected by copyright, whether you put a “© copygirl” or something to that effect on it or not. To use someone else’s work, you either need to get permission from the author directly, or the work has to be available under a license that says you’re allowed to (typically comes with some requirements or restrictions). One can also release a work under public domain, but that isn’t legally possible in some countries. There’s also some exceptions like fair use but that’s another thing.