Repository navigation
Status: the function the third deploy missed is deployed too - #318
Merged
Merged
Conversation
onUserUpdated was not updated by the full deploy: two of its update requests were refused as too many at once, and the deploy did not try again. Deployed on its own afterwards, it now runs the same code as the other 66. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Corrects one line in
STATUS.md.Why the full deploy missed
onUserUpdated. During the deploy, the Cloud Functions API refused two of itsUpdateFunctionrequests with 429, and the deploy did not try them again.Now. It was deployed on its own afterwards. All 67 functions run the same code, and the deployed code is byte for byte the deploy tree's. There have been no warnings or errors since.
🤖 Generated with Claude Code