Report staging update and sign-in failures safely - #126
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe staging update probe now reports structured validation details. The staging end-to-end test sends the staging origin during owner sign-in and includes the HTTP status in assertion failures. ChangesStaging update flow
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This improves staging upgrade and sign-in failure diagnostics without changing product behavior, authentication behavior, schemas, or release artifacts. No current merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The public upgrade gate stopped with a same-version repair error even during a version upgrade. Report which of the five strict status checks failed as booleans, without logging response values. The checks remain unchanged.
The channel E2E test now sends the same explicit origin as the other staging sign-in tests and includes the HTTP status when sign-in fails. This makes the two failures in public run 34142366293 actionable.
Validation: full local check passed (946 unit tests, 216 integration tests, coverage, architecture, and build); deployment dry run passed. A fresh public upgrade run will verify both paths after merge. No product behavior, signed archive, or schema changes.
Summary by CodeRabbit