sharpetronics/stripe-ruby
1
0
Fork 0
mirror of https://github.com/stripe/stripe-ruby.git synced 2025-10-18 00:01:04 -04:00
Code Issues Projects Releases Wiki Activity

Merge pull request #1383 from stripe/latest-codegen-beta

Browse Source 
Update generated code for beta
This commit is contained in:
stripe-openapi[bot] 2024-04-18 14:36:38 -07:00 committed by GitHub
commit 99c81c7074
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
5 changed files with 14 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CHANGELOG.md
View File

@ -1,5 +1,9 @@
# Changelog # Changelog
## 11.1.0 - 2024-04-16
* [#1379](https://github.com/stripe/stripe-ruby/pull/1379) Update generated code
* Add support for new resource `Entitlements.ActiveEntitlementSummary`
## 11.1.0-beta.1 - 2024-04-11 ## 11.1.0-beta.1 - 2024-04-11
* [#1376](https://github.com/stripe/stripe-ruby/pull/1376) Update generated code for beta * [#1376](https://github.com/stripe/stripe-ruby/pull/1376) Update generated code for beta
* Add support for `retrieve` method on resources `Entitlements.ActiveEntitlement` and `Entitlements.Feature` * Add support for `retrieve` method on resources `Entitlements.ActiveEntitlement` and `Entitlements.Feature`
@ -2037,3 +2041,4 @@ Identical to 1.56.0 above. I incorrectly cut a patch-level release.
<!-- <!--
# vim: set tw=0: # vim: set tw=0:
--> -->

2
OPENAPI_VERSION
View File

@ -1 +1 @@
v950 v962

2
lib/stripe/api_version.rb
View File

@ -4,6 +4,6 @@
module Stripe module Stripe
module ApiVersion module ApiVersion
CURRENT = "2024-04-10" CURRENT = "2024-04-10"
PREVIEW = "2024-03-20.preview-v2" PREVIEW = "2024-04-11.preview-v2"
end end
end end

6
lib/stripe/resources/forwarding/request.rb
View File

@ -3,9 +3,9 @@
module Stripe module Stripe
module Forwarding module Forwarding
# Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config. # Instructs Stripe to make a request on your behalf using the destination URL. The destination URL
# A config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with # is activated by Stripe at the time of onboarding. Stripe verifies requests with your credentials
# your credentials in the config, and injects card details from the payment_method into the request. # provided during onboarding, and injects card details from the payment_method into the request.
# #
# Stripe redacts all sensitive fields and headers, including authentication credentials and card numbers, # Stripe redacts all sensitive fields and headers, including authentication credentials and card numbers,
# before storing the request and response data in the forwarding Request object, which are subject to a # before storing the request and response data in the forwarding Request object, which are subject to a

8
lib/stripe/resources/setup_intent.rb
View File

@ -8,13 +8,13 @@ module Stripe
# #
# Create a SetupIntent when you're ready to collect your customer's payment credentials. # Create a SetupIntent when you're ready to collect your customer's payment credentials.
# Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid. # Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid.
# The SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides # The SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides
# you through the setup process. # you through the setup process.
# #
# Successful SetupIntents result in payment credentials that are optimized for future payments. # Successful SetupIntents result in payment credentials that are optimized for future payments.
# For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through # For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through
# [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection # [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection
# to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents). # to streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).
# If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer), # If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),
# it automatically attaches the resulting payment method to that Customer after successful setup. # it automatically attaches the resulting payment method to that Customer after successful setup.
# We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on # We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on
@ -22,7 +22,7 @@ module Stripe
# #
# By using SetupIntents, you can reduce friction for your customers, even as regulations change over time. # By using SetupIntents, you can reduce friction for your customers, even as regulations change over time.
# #
# Related guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents) # Related guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)
class SetupIntent < APIResource class SetupIntent < APIResource
extend Stripe::APIOperations::Create extend Stripe::APIOperations::Create
extend Stripe::APIOperations::List extend Stripe::APIOperations::List