fix(ci): remove expiring OAuth token deploy gate - #657
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (4)
💤 Files with no reviewable changes (1)
Included review availability: 3 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 6 reviews per hour. 📝 WalkthroughWalkthroughChangesProduction MCP validation
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to Production deployment no longer depends on an expiring user token, while read-only health and authentication checks remain automated and authenticated checks remain available to operators. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
agent-paste PR preview resources were cleaned up. The shared Preview GitHub Environment is retained for future preview deploys. |
Summary
Production deploys fail after successfully deploying the Workers because the MCP smoke uses a stored, short-lived user OAuth token. Run 35007586363 failed with
initialize returned 401.Changes
Risk: LOW
Workflow and documentation change. Deployment no longer asserts authenticated MCP tool calls. Runtime authentication and authorization are unchanged.
Test plan
pnpm verifyactionlint .github/workflows/deploy-production.ymlpnpm smoke:prod:readonly, passed against productiongit diff --checkNeed help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit
Deployment
Documentation