Repository navigation
Promote staging monitoring fixes to production - #513
Merged
Merged
Conversation
…atch fix(ci): enable container image dispatch from default branch
fix(ci): build staging images with isolated public settings
…nd-monitoring fix(sentry): restore server error reporting
…loyments ci: deploy staging and production images after CI
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
 |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 39 files
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
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.
Description
Promote the monitoring and deployment changes verified on staging. Report handled web and mobile tRPC server failures to Sentry while preserving responses and expected 4xx handling. Keep catalog downloads off the startup path, share concurrent loads and prevent stale refreshes from replacing current data.
Enable CI-gated image publication and deployment on master. Preserve production's Next.js 16.3.6, complete dependency lockfile and Prisma tree, including nullable report attribution and the existing deletion migration. Production's account-deletion and crawler fixes remain in place. No hosted migration or DNS change.
Type of change
How Has This Been Tested?
Screenshots (if applicable)
Not applicable.
Checklist
Notes for reviewers
The promotion branch starts from master and merges staging, preserving both histories. Staging verification used Next.js 16.2.6; production's preserved 16.3.6 passed its own CI and runtime verification. Production's account-deletion database check remains in CI.
A fresh encrypted backup was verified before merging. Master CI built a new image with production settings, deployed it and verified its exact commit and readiness. Production credentials, database schema and DNS remain unchanged.
Review follow-up covers omitted Clerk settings, both deployment-command guards and malformed health JSON. Failed deployment selection remains manual recovery: a failed API response may still have queued a deployment, so automatic restoration would race it.
Review validation: this app has no Edge routes and Next.js 16 Proxy uses Node. The installed dotenv CLI preserves CI variables when its optional file is absent; migration steps passed on the runner. Sentry 10.53.1 deduplicates repeated capture of the same Error object, confirmed with an in-memory transport.
Production verification:
4243fe6eis healthy, normal page navigation and report details load, and Sentry received the production test event. Rollout briefly hit Supabase's 15-session limit from 09:32:06–09:32:42 UTC, ending before deployment verification completed. No recurrence during the next ten minutes. Pool configuration is unchanged; connection budgeting remains an operational follow-up. CodeRabbit skipped this master-target PR under its existing branch policy.