Turbopack: more strict vergen setup#93541
Merged
Merged
Conversation
Contributor
Stats from current PR✅ No significant changes detected📊 All Metrics📖 Metrics GlossaryDev Server Metrics:
Build Metrics:
Change Thresholds:
⚡ Dev Server
📦 Dev Server (Webpack) (Legacy)📦 Dev Server (Webpack)
⚡ Production Builds
📦 Production Builds (Webpack) (Legacy)📦 Production Builds (Webpack)
📦 Bundle SizesBundle Sizes⚡ TurbopackClient Main Bundles
Server Middleware
Build DetailsBuild Manifests
📦 WebpackClient Main Bundles
Polyfills
Pages
Server Edge SSR
Middleware
Build DetailsBuild Manifests
Build Cache
🔄 Shared (bundler-independent)Runtimes
📎 Tarball URLCommit: 29622c6 |
sokra
approved these changes
May 6, 2026
Contributor
Tests PassedCommit: 29622c6 |
The vergen-gitcl build script in next-napi-bindings calls git rev-parse, which fails with "dubious ownership in repository at '/build'" because the bind-mounted workspace is owned by a different uid than the container's root user.
This was referenced May 7, 2026
eps1lon
added a commit
that referenced
this pull request
May 7, 2026
Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Sebastian Sebbie Silbermann <sebastian.silbermann@vercel.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
We were getting these errors and they didn't fail the build:
The issue comes from a change in Git 2.35 which started to refuse working on Git directories that were owned by a different uid. Our self-hosted runners used 2.34.1 whereas GH hosted runners use 2.50.
This PR:
fail_on_erroris moved beforeadd_instructionsso git errors actually fail the build instead of being emitted as silent warnings).git rev-parse HEADerror reporting incrates/next-napi-bindings/build.rsso the underlying status/stderr is surfaced.git config --global --add safe.directory /buildtoscripts/docker-native-build.shso the bind-mounted workspace is accepted by Git inside the native build container.Test plan
Without adding the safe directory we actually get the dubious ownership error:
With the fix