oficina / memoria Public

release-target

make release now means the same thing in every Oficina app: it builds a linux/arm64 binary into releases/<app>-linux-arm64, stamped with the version it will be published under.

Why the stamp changed. rastrillo.BuildVersion defaults to dev, and that is the field the deploy check reads back from GET /api/version. An unstamped binary answers dev from every build ever made, so the check compares a constant against a constant and cannot fail. This repo already knew that — the stamp was a short sha. Now that a release is a tag, git describe --tags --always resolves to the tag when the build sits on one and falls back to the same short sha when it does not, so nothing is lost and a published binary reports the name it was published under.

Why the path and the name. amadan release create uploads a file under its basename, and neither a release nor its files can be deleted once they exist, so the name is permanent on the first try or not at all.

Verified: the target builds, file reports ELF 64-bit LSB executable, ARM aarch64, and the version string is present in the binary.

Commits 0
Discussions 1 1 open
Tasks 0/0 done

Activity