Repository navigation
fix(applyflow): gate cloud rollout by account allowlist - #258
Merged
Merged
Conversation
A global flag alone would reactivate every existing v2_cloud account. Selection now fails closed, and the ignore helper avoids the turbo-ignore false skip without disabling portal-only skips.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Pin synthetic account ids so the server allowlist can distinguish active, read-only, and paused, and keep the A-to-B switch on selected cloud accounts.
This branch was successfully deployed
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
APPLYFLOW_PERSISTENCE_V2_ROLLOUT_ACCOUNTSselects which accounts may leave v1 or v2_paused when the global flag is on. An absent, empty, or invalid list fails closed. Existingv2_cloudaccounts that are not listed stay paused without changingcanonicalPersistenceor falling back to local storage.scripts/applyflow-vercel-ignore.mjsavoids the turbo-ignore false skip caused by combiningVERCEL_GIT_PREVIOUS_SHAwith the same SHA in--filter. Portal-only diffs can still skip. The Vercel project command is unchanged.Test plan
/meroutes (166 passed)node --test scripts/applyflow-vercel-ignore.test.mjs18cf6620, exit 0 vsbe7a346cwithVERCEL=1APPLYFLOW_PERSISTENCE_V2on from this PR