Merge breaking changes from sdk-release/next-major branch to master #3065
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.
Why?
The March monthly API release is going to contain breaking changes. Therefore, we will be shipping a new major version. This PR pulls in the breaking changes in the SDKs that were staged in the sdk-release/next-major branch
What?
sdk-release/next-majorInvoiceUpcomingLinesServicefile - it was deleted in master but survived the merge in the previous stepChangelog
StripeAccountandStripeContexttoStripeClientOptions, so you can specify the Stripe-Account or Stripe-Context header at the client (instead of the individual request) level. See PR #3058ApiModefromRawRequestOptions. ApiMode is automatically determined from the path passed to RawRequest. See PR #3052ServiceNestedandService<T>classes. To implement custom services, use the request methods defined onStripeClient. See PR #3051ListAutoPagingandListAutoPagingAsyncto not mutate options object passed in. See PR #2899