Release v3.33.0 - #137
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
Warning Review limit reachedNext included review available in 4 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (7)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (11)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe PR makes PC-V1 resource and request fields optional in TypeScript declarations. It updates package version metadata and adds a v3.33.0 changelog entry. ChangesPC-V1 Type Optionality
Release Versioning
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to This release makes PC-V1-only fields optional in the TypeScript SDK so PC-V2 responses and related inputs can omit them without type errors. The declaration updates and v3.33.0 version metadata are consistent, with no current merge-blocking risk identified. Assessment against linked issues
Suggested reviewers: 🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
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 |
- PC-V1 attributes are now optional in TypeScript types (Subscription, Coupon, HostedPage, Quote, QuotedSubscription, Estimate, Gift) - PC-V1 and PC-V2 APIs coexist; PC-V1-only fields must not be required Co-authored-by: Cursor <cursoragent@cursor.com>
a405834 to
e67d745
Compare
v3.33.0
Bug Fixes
plan_id,plan_quantity,plan_constraint,addon_constraint,embed, etc.) are now typed as optional across all affected resources (Subscription,Coupon,HostedPage,Quote,QuotedSubscription,Estimate,Gift).Why: PC-V1 and PC-V2 APIs coexist in the same Chargebee environment. PC-V1-only fields are absent in PC-V2 responses, so marking them as required caused incorrect TypeScript type errors for PC-V2 users.
Generator fix: chargebee/sdk-generator#112
Made with Cursor
Updated v3.33.0 TypeScript typings to make PC-V1-only fields optional across affected resources and request parameters. This supports environments where PC-V2 responses omit fields such as
plan_id,plan_quantity,plan_constraint,addon_constraint, andembed.