chore: regenerate SDK from latest API spec#193
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (59)
📒 Files selected for processing (5)
WalkthroughThe management SDK was regenerated with additional directory, organization invite, passkey, permission, update, and identity artifacts. Package exports and API exposure tests were expanded, while generator and SDK version metadata changed from 2.0.0 to 2.3.0. ChangesManagement SDK regeneration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Explain your changes
Syncs the generated management client with the live management API spec
Checklist
🛟 If you need help, consider asking for advice over in the Kinde community.