chore: wire CLI version via ldflags at build time

[kriscoleman]

This PR

Added ldflags configuration to GoReleaser and Makefile to inject the actual CLI version, commit hash, and build date at compile time.

This ensures:

• GoReleaser builds embed the release version from git tags
• Local builds via make build use git describe for versioning
• The version command displays accurate version info instead of "dev"

Related Issues

Closes #192

How to test

To see the behavior when you built locally prior to this change, pull main and run make install then run openfeature and notice:

To see the behavior after this change, pull this branch, run make install and then run openfeature and notice more meaninful meta:

[gemini-code-assist]

Summary of Changes

Hello @kriscoleman, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the build process by integrating dynamic versioning information into the CLI binary. By leveraging ldflags, it ensures that both official releases and local development builds accurately reflect the current version, commit, and build date, thereby improving the clarity and traceability of the compiled application.

Highlights

• Accurate Versioning: Implemented ldflags configuration in both GoReleaser and the Makefile to inject the actual CLI version, commit hash, and build date directly into the compiled binary at compile time.
• Build Process Enhancement: Ensures that GoReleaser builds embed the release version derived from git tags, while local builds executed via make build utilize git describe for dynamic versioning.
• Improved User Experience: The version command of the CLI will now display accurate and meaningful metadata instead of a generic 'dev' placeholder, providing better context for users.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a solid improvement by embedding version information into the CLI binary at build time using ldflags. The changes in both .goreleaser.yaml and the Makefile correctly implement this for both release and local builds. My review includes a couple of minor suggestions to improve consistency between the two build methods and to make the local build process more robust against custom variable values.

[erka]

runtime/debug.BuildInfo.Main.Version could be a better option

[erka]

go install github.com/erka/gobuild@v0.0.1 as example

[georgesdugue]

Testing: Looks great

main

this branch