Skip to content

fix: restore short git SHA in version banner#47

Merged
nerdCopter merged 1 commit into
masterfrom
fix/short-git-sha
Jul 2, 2026
Merged

fix: restore short git SHA in version banner#47
nerdCopter merged 1 commit into
masterfrom
fix/short-git-sha

Conversation

@nerdCopter

Copy link
Copy Markdown
Owner

AI Generated pull-request

Summary

  • The vergen 8 -> vergen-gitcl 10 migration (build: cargo update and vergen 8 -> vergen-gitcl 10 #44) switched build.rs from EmitBuilder::git_sha(true) (short SHA) to Gitcl::all_git(), which emits the full 40-char VERGEN_GIT_SHA instead.
  • Regression: bbl_parser --version now prints the full SHA (bbl_parser 1.0.1 76b67b5d7a48cb79125ab18be6864c77f44bbb9d (2026-07-02)) instead of the short one used since 1.0.0 (bbl_parser 1.0.0 03b87d3 (2025-12-30)).
  • Fix: Gitcl::all().sha(true).build() keeps all other VERGEN_GIT_* instructions enabled while restoring short-SHA output (Gitcl::builder().all() is a private crate-internal method, so Gitcl::all() is the public equivalent).

Test plan

  • cargo build --release and cargo test --release pass (19 unit/integration tests + 3 doc-tests)
  • bbl_parser --version now prints a 7-char short SHA (e.g. 61448ef)

The vergen 8 -> vergen-gitcl 10 migration (build: upgrade vergen 8 ->
vergen-gitcl 10) switched from EmitBuilder::git_sha(true) (short SHA)
to Gitcl::all_git(), which defaults to the full 40-char SHA. The
version banner (bbl_parser 1.0.1 <sha> (<date>)) now prints the full
hash instead of the short one used since 1.0.0.

Use Gitcl::all().sha(true).build() to restore short-SHA output while
keeping all other VERGEN_GIT_* instructions enabled.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nerdCopter, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f6e08b19-c573-4689-9c24-0850171a657f

📥 Commits

Reviewing files that changed from the base of the PR and between 61448ef and 9afb8ac.

📒 Files selected for processing (1)
  • build.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/short-git-sha

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@nerdCopter nerdCopter marked this pull request as ready for review July 2, 2026 20:41
@nerdCopter nerdCopter merged commit eb5f3a5 into master Jul 2, 2026
9 checks passed
@nerdCopter nerdCopter deleted the fix/short-git-sha branch July 2, 2026 20:45
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