The API build_info fields (version, commit, build_time) are always empty strings because no build-time variables are set in the Dockerfile

[Lost-Z]

Summary

The /health endpoint response includes version, commit, and build_time fields sourced from state.build_info. These values are intended to identify the deployed binary. However the Dockerfile does not set the corresponding CARGO_PKG_VERSION, GIT_COMMIT, or BUILD_TIME environment variables during the build step. As a result, all three fields are empty strings in every Docker-based deployment, making it impossible to identify which version is running from the health endpoint.

Expected Behavior

The /health endpoint should return the actual version, git commit SHA, and build timestamp of the running binary.

Proposed Solution

• Add ARG GIT_COMMIT, ARG BUILD_TIME to the Dockerfile builder stage and pass them as ENV variables
• Set them in docker-compose.full.yml and in the docker-publish CI workflow using --build-arg
• Read them in the application's main.rs using std::env::var at startup

Affected Files

• Dockerfile
• docker-compose.full.yml
• .github/workflows/docker-publish.yml

[Emzux]

@Emzux has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I’ve reviewed the issue details and I’m ready to contribute a clean solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emzux to this issue.

[isaacaabot]

@isaacaabot has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to apply for this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @isaacaabot to this issue.

[CodedTricks]

@CodedTricks has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @CodedTricks to this issue.

[drips-wave]

Congratulations, @CodedTricks! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @CodedTricks: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @CodedTricks as part of the Stellar Wave Program's 8th Wave 🥳

😎 @CodedTricks: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.