Post preview expectations before build - #605
Merged
Merged
Conversation
Contributor
❌ Develop S3 preview failed
The ordinary generated Vercel Preview remains available on the shared development runtime. Re-run this workflow after correcting the deployment, DNS, or CORS configuration. Generic Vercel Preview deployments use the shared development runtime; this controller adds the stable exact-SHA alias and marker-scoped cleanup. |
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.
Summary
pnpm@10.12.1Corepack bootstrap up to three times in both secretless build paths after a live transient Node/Undici transport assertionValidation
git diff --check: passLive evidence prompting the bootstrap retry
Run 33754126360 reached the new exact-SHA all-base controller but a single
corepack prepare pnpm@10.12.1process hit Node's Undiciassert(!this.paused)transport assertion. Run 33741566074 attempt 2 succeeded end-to-end for PR #595 at the exact same pinned toolchain and established the expected deployment/alias proof.