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.
This PR contains the following updates:
12.6.0
->13.3.1
Release Notes
stripe/stripe-ruby (stripe)
v13.3.1
Compare Source
StripeClient
was not falling back to global options for options that are not available to be set per-clientlivemode
and optionalreason
fields to ThinEventv13.3.0
Compare Source
#1500 This release changes the pinned API version to
2024-12-18.acacia
.#1507 Pass requestor to all deserialized objects including lists
StripeObject
retrieved from lists could not be used to make requests, such asrefresh
v13.2.0
Compare Source
2024-11-20.acacia
.respond
test helper method on resourceIssuing.Authorization
v13.1.2
Compare Source
v13.1.1
Compare Source
stripe_version
v13.1.0
Compare Source
2024-10-28.acacia
.submit_card
test helper method on resourceIssuing.Card
V2.EventDestinations
create
,retrieve
,update
,list
,delete
,disable
,enable
andping
methods on resourceV2.EventDestinations
StripeObject
for custom resources. They should now return the instance of the custom resource.v13.0.2
Compare Source
#1473 Always return the result of APIResource#refresh in APIResource.retrieve
self
object when callingAPIResource.retrieve
v13.0.1
Compare Source
#1471 update object tags for meter-related classes
object
property of theMeterEvent
,MeterEventAdjustment
, andMeterEventSession
didn't match the server.#1470 Cleaned up examples and added documentation
v13.0.0
Compare Source
#1458 Support for APIs in the new API version 2024-09-30.acacia
This release changes the pinned API version to
2024-09-30.acacia
. Please read the API Upgrade Guide and carefully review the API changes before upgrading.Please refer to our migration guide for v13 for more information about the backwards incompatible changes.
❗
StripeClient
and related changesStripeClient
and requestor logic toAPIRequestor
.StripeClient#request
is still available, but is deprecated and will be removed. We encourageStripeClient#raw_request
as a replacement (see other breaking changes for more detail).StripeClient
as the the entry-point to the service-based pattern, a new interface for calling the Stripe API with many benefits over the existing resource-based paradigm. Services are available under thev1
andv2
accessors.retrieve
before doing anupdate
.Other breaking changes
0
->2
2
->5
StripeClient#connection_manager
. This was a legacy method from years ago.retrieve
method now requiresparams
to be passed as the first argument. Existing calls to singletonretrieve
method with onlyopts
argument will have to be updated to account for the addition ofparams
argument.❌ No longer works
✅ Correct way to call retrieve method
Stripe.raw_request()
method that was recently added toStripeClient
. This will use the configuration set on the StripeClient instead of the global configuration used before.APIResource.request
. Instead, useStripeClient#raw_request
now.Instead of
do
APIResource.execute_resource_request
. However, we discourage use of this in favor ofStripeClient#raw_request
.is now, with base_address being one of [:api, :files, :connect, :meter_events]
APIRequestor.execute_request
(previouslyStripeClient.execute_request
). It now returns all request options from our internal request framework as the second value in the returned tuple, instead of only the API key used:Before
is now, with base_address being one of [:api, :files, :connect, :meter_events]
Additions
Billing.MeterEvent
,Billing.MeterEventAdjustments
,Billing.MeterEventSession
,Billing.MeterEventStream
and the new Events APICore.Events
in the v2 namespaceparse_thin_event()
on theStripeClient
class to parse thin events.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.