update to latest vergen#1770
Merged
Merged
Conversation
jgallagher
commented
Sep 17, 2025
| [build-dependencies] | ||
| vergen = { version = "8.3.2", features = ["cargo", "git", "git2", "rustc" ] } | ||
| vergen = { version = "9.0.6", features = ["cargo", "rustc"] } | ||
| vergen-git2 = "1.0.7" |
Contributor
Author
There was a problem hiding this comment.
We could use vergen-gix instead to avoid linking against libgit2 altogether? But that pulled in a lot more Cargo.lock changes, so I just went with the successor to what we had before (vergen 8's git2 feature).
leftwo
approved these changes
Sep 17, 2025
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.
I diffed the build script output before and after this change, and all the
VERGEN_*env variable output was identical. The exact changes (which seem fine?) were