Include git commit hash in SQL extension version#8
Merged
Conversation
Co-authored-by: bcho <1975118+bcho@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Attach git commit to sql extension version
Include git commit hash in SQL extension version
Jan 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
absurd_version()SQL function now returns the git commit hash alongside the package version for better build traceability.Changes
git rev-parse --short HEAD, expose asGIT_COMMITenv var (defaults to "unknown" if git unavailable)absurd_version()to return formatabsurd-sqlite/{version} ({commit})Example
The commit hash updates automatically on each build, allowing deployed extensions to be traced back to their exact source code state.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.