Update generated code for beta

CHANGELOG.md

@@ -1,5 +1,9 @@
 # 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
 * [#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`
@@ -2037,3 +2041,4 @@ Identical to 1.56.0 above. I incorrectly cut a patch-level release.
 <!--
 # vim: set tw=0:
 -->
+

OPENAPI_VERSION

@@ -1 +1 @@
-v950
+v962

lib/stripe/api_version.rb

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

lib/stripe/resources/forwarding/request.rb

@@ -3,9 +3,9 @@
 
 module Stripe
   module Forwarding
-    # Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config.
-    # A config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with
-    # your credentials in the config, and injects card details from the payment_method into the request.
+    # Instructs Stripe to make a request on your behalf using the destination URL. The destination URL
+    # is activated by Stripe at the time of onboarding. Stripe verifies requests with your credentials
+    # 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,
     # before storing the request and response data in the forwarding Request object, which are subject to a

lib/stripe/resources/setup_intent.rb

@@ -8,21 +8,21 @@ module Stripe
   #
   # 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.
-  # 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.
   #
   # 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
-  # [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection
-  # to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
+  # [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection
+  # 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),
   # 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
   # PaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.
   #
   # 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
     extend Stripe::APIOperations::Create
     extend Stripe::APIOperations::List