Bump stripe/stripe-php from 9.8.0 to 12.0.0 in /server/php

[dependabot]

Bumps stripe/stripe-php from 9.8.0 to 12.0.0.

Release notes

Sourced from stripe/stripe-php's releases.

v12.0.0

11.0.0 - 2023-08-16

Note: please use stripe-php v12.0.0 and do not use v11.0.0. In v11, StripeClient does not correctly apply the new pinning behavior.

⚠️ ACTION REQUIRED: the breaking change in this release likely affects you ⚠️

See the changelog for more details.

v11.0.0

⚠️ ACTION REQUIRED: the breaking change in this release likely affects you ⚠️

Version pinning

In this release, Stripe API Version 2023-08-16 (the latest at time of release) will be sent by default on all requests. This is a significant change with wide ramifications. The API version affects the properties you see on responses, the parameters you are allowed to send on requests, and so on. The previous default was to use your Stripe account's default API version.

To successfully upgrade to stripe-php v11, you must either

1. (Recommended) Upgrade your integration to be compatible with API Version 2023-08-16.

   Please read the API Changelog carefully for each API Version from 2023-08-16 back to your Stripe account's default API version. Determine if you are using any of the APIs that have changed in a breaking way, and adjust your integration accordingly. Carefully test your changes with Stripe Test Mode before deploying them to production.

   You can read the v11 migration guide for more detailed instructions.

2. (Alternative option) Specify a version other than 2023-08-16 when initializing stripe-php.

   If you were previously initializing stripe-php without an explicit API Version, you can postpone modifying your integration by specifying a version equal to your Stripe account's default API version. For example:

     // if using StripeClient
   - $stripe = new \Stripe\StripeClient('sk_test_xyz');
   + $stripe = new \Stripe\StripeClient([
   +   'api_key' => 'sk_test_xyz',
       'stripe_version' => '2020-08-27',
   + ]);
   // if using the global client
   Stripe.apiKey = "sk_test_xyz";
   
   Stripe::setApiVersion('2020-08-27');

If you were already initializing stripe-php with an explicit API Version, upgrading to v11 will not affect your integration.

Read the v11 migration guide for more details.

Going forward, each major release of this library will be pinned by default to the latest Stripe API Version at the time of release.

That is, instead of upgrading stripe-php and separately upgrading your Stripe API Version through the Stripe Dashboard, whenever you upgrade major versions of stripe-php, you should also upgrade your integration to be compatible with the latest Stripe API version.

Other changes in v11.0.0

" ⚠️" symbol highlights breaking changes.

... (truncated)

Changelog

Sourced from stripe/stripe-php's changelog.

12.0.0 - 2023-08-18

⚠️ ACTION REQUIRED: the breaking change in this release likely affects you ⚠️

Version pinning

In this release, Stripe API Version 2023-08-16 (the latest at time of release) will be sent by default on all requests. This is a significant change with wide ramifications. The API version affects the properties you see on responses, the parameters you are allowed to send on requests, and so on. The previous default was to use your Stripe account's default API version.

To successfully upgrade to stripe-php v12, you must either

1. (Recommended) Upgrade your integration to be compatible with API Version 2023-08-16.

   Please read the API Changelog carefully for each API Version from 2023-08-16 back to your Stripe account's default API version. Determine if you are using any of the APIs that have changed in a breaking way, and adjust your integration accordingly. Carefully test your changes with Stripe Test Mode before deploying them to production.

   You can read the v12 migration guide for more detailed instructions.

2. (Alternative option) Specify a version other than 2023-08-16 when initializing stripe-php.

   If you were previously initializing stripe-php without an explicit API Version, you can postpone modifying your integration by specifying a version equal to your Stripe account's default API version. For example:

     // if using StripeClient
   - $stripe = new \Stripe\StripeClient('sk_test_xyz');
   + $stripe = new \Stripe\StripeClient([
   +   'api_key' => 'sk_test_xyz',
       'stripe_version' => '2020-08-27',
   + ]);
   // if using the global client
   Stripe.apiKey = "sk_test_xyz";
   
   Stripe::setApiVersion('2020-08-27');

If you were already initializing stripe-php with an explicit API Version, upgrading to v12 will not affect your integration.

Read the v12 migration guide for more details.

Going forward, each major release of this library will be pinned by default to the latest Stripe API Version at the time of release.

That is, instead of upgrading stripe-php and separately upgrading your Stripe API Version through the Stripe Dashboard, whenever you upgrade major versions of stripe-php, you should also upgrade your integration to be compatible with the latest Stripe API version.

Other changes

" ⚠️" symbol highlights breaking changes.

• #1553⚠️ Remove deprecated enum value Invoice.STATUS_DELETE

• #1550 PHPDoc changes

  • Remove support for alternate_statement_descriptors, destination, and dispute on Charge
  • Remove support for value charge_refunded from enum Dispute.status
  • Remove support for rendering on Invoice
  • Remove support for attributes, caption, and deactivate_on on Product

11.0.0 - 2023-08-16

... (truncated)

Commits

• 732996b Bump version to 12.0.0
• 7977510 Merge pull request #1555 from stripe/richardm-fix-pinning-for-stripeclient
• 68086b4 format
• f845b4c Fix pinning for stripeclient
• 8860217 Update CHANGELOG.md
• bd6dfe6 Grammar in CHANGELOG.md
• 19db5a3 Bump version to 11.0.0
• f44f74a Update generated code (#1550)
• 2f6758f Merge pull request #1542 from stripe/sdk-release/next-major
• 22a5dc5 Merge pull request #1553 from stripe/richardm-remove-invoice-status-delete
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)