Disable Vercel auto-deploys on main; rely on deploy hook#31
Merged
Conversation
….yml The previous ignoreCommand approach raced the release workflow: Vercel's shallow clone + tag fetch couldn't resolve the just-pushed tag with `git describe --exact-match`, so even hook-triggered deploys got canceled. Switch to Vercel's git.deploymentEnabled flag, which suppresses auto deploys on main without affecting deploy hooks. The hook fired from release.yml after tagging now provides the only production path, so the build always sees the tagged commit. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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
ignoreCommandwith Vercel'sgit.deploymentEnabled.main: falseflag.main. The deploy hook fired byrelease.yml(after tag push) becomes the only production path.Why
Last attempt's
ignoreCommandcanceled both the auto-deploy AND the hook-triggered deploy forbe43569—git describe --exact-match --tags HEADdoesn't resolve reliably in Vercel's shallow clone, so even after the tag was pushed, the check returned "ignore".git.deploymentEnabledis Vercel's official way to suppress auto-deploys for a branch and is bypassed by deploy hooks, removing the race entirely.Test plan
releaseworkflow tags + hits deploy hook.vX.Y.Z(not a SHA).🤖 Generated with Claude Code