Skip to content

Use the 12-character sha in release builds; record v0.1.0 in the plan - #2

Merged
jqnatividad merged 2 commits into
dathere:mainfrom
jqnatividad:main
Oct 13, 2026
Merged

jqnatividad merged 2 commits into
dathere:mainfrom
jqnatividad:main

Conversation

@jqnatividad

Copy link
Copy Markdown
Contributor

Two follow-ups to v0.1.0:

  • Release binaries embed the 12-character git sha (29ebab6). v0.1.0 binaries report the full 40-character sha, while Docker and local builds report 12. Both release build steps now pass ${GITHUB_SHA::12}, as ci.yml's docker job already does.
  • PLAN.md §13.1 records the v0.1.0 release (9185ed1): the merge, the tag and release runs, and the fork → upstream workflow (merge with a merge commit; push tags to upstream only).

CI on the fork is green for 9185ed1 (fmt, clippy, tests, cargo-deny, Docker build). The sha change takes effect on the next release.

Please merge with a merge commit, as with #1.

🤖 Generated with Claude Code

jqnatividad and others added 2 commits October 12, 2026 21:53
Release builds passed the full github.sha, so v0.1.0 binaries report a
40-character sha while Docker and local builds report 12 (build.rs uses
rev-parse --short=12). Both release build steps now pass GITHUB_SHA::12,
as ci.yml's docker job already does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jqnatividad
jqnatividad merged commit 5023f89 into dathere:main Oct 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant