fix: automate firestore deploy + unblock verify-local from e2e hangs#7
Merged
shadowdevcode merged 1 commit intomainfrom Mar 25, 2026
Merged
Conversation
|
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\n- add automated Firestore rules deploy on main when Firestore files change\n- add production smoke check for unknown ingredient queue (owner allowed, non-member denied)\n- add build-id diagnostics for unknown queue permission errors\n- split CI verification into blocking core checks and non-blocking e2e to prevent deploy blockage\n\n## Validation\n- npm run verify:core passed locally\n- npm run rules:target:check passed\n- npm run lint passed\n- npm run unit:test passed\n- npm run build passed\n- npm run rules:test passed\n