build(deps): bump stripe from 2.68.0 to 6.2.0

[dependabot[bot]]

Bumps stripe from 2.68.0 to 6.2.0.

Release notes

Sourced from stripe's releases.

v6.2.0

• #1024 Update generated code
  • Add support for new resource AccountSession
  • Add support for create method on resource AccountSession
• #1032 Types for CRUDL methods on parents

See the changelog for more details.

v6.1.0

• #1016 Update generated code
• #1020 Adds type annotations, and dependency on typing_extensions.

See the changelog for more details.

v6.1.0b2

• #1006 #1017 Update generated code for beta
• #1020 Adds type_annotations, and dependency on typing_extensions.

See the changelog for more details.

v6.1.0b1

• #1017
  • Updated stable APIs to the latest version

See the changelog for more details.

v6.0.0

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

• #1001 #1008 Remove support for Python 2.

  • The last version of stripe-python that supports Python 2 is 5.5.0. The Python Software Foundation (PSF) community announced the end of support of Python 2 on 01 January 2020. To continue to get new features and security updates, please make sure to update your Python runtime to Python 3.6+.

• #987 ⚠️⚠️Pin to the latest API version⚠️⚠️

  In this release, Stripe API Version 2023-08-16 (the latest at time of release) will be sent by default on all requests. The previous default was to use your Stripe account's default API version.

  To successfully upgrade to stripe-python v6, 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 v6 migration guide for more detailed instructions.

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

     If you were previously initializing stripe-python 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:

       import stripe
       stripe.api_key = "sk_test_..."
     

... (truncated)

Changelog

Sourced from stripe's changelog.

6.2.0 - 2023-08-31

• #1024 Update generated code
  • Add support for new resource AccountSession
  • Add support for create method on resource AccountSession
• #1032 Types for CRUDL methods on parents

6.1.0 - 2023-08-24

• #1016 Update generated code
• #1020 Adds type annotations, and dependency on typing_extensions.

6.0.0 - 2023-08-16

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

• #1001 #1008 Remove support for Python 2.

  • The last version of stripe-python that supports Python 2 is 5.5.0. The Python Software Foundation (PSF) community announced the end of support of Python 2 on 01 January 2020. To continue to get new features and security updates, please make sure to update your Python runtime to Python 3.6+.

• #987 ⚠️⚠️Pin to the latest API version⚠️⚠️

  In this release, Stripe API Version 2023-08-16 (the latest at time of release) will be sent by default on all requests. The previous default was to use your Stripe account's default API version.

  To successfully upgrade to stripe-python v6, 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 v6 migration guide for more detailed instructions.

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

     If you were previously initializing stripe-python 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:

       import stripe
       stripe.api_key = "sk_test_..."
     + stripe.api_version = '2020-08-27'
     

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

     Read the v6 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-python and separately upgrading your Stripe API Version through the Stripe Dashboard, whenever you upgrade major versions of stripe-python, you should also upgrade your integration to be compatible with the latest Stripe API version.

• #1013 ⚠️Removed @​test_helper decorator

  • This is technically breaking but unlikely to affect most users.

• #1015 ⚠️Assert types of pagination responses

  • Pagination will raise an exception if the API response is not of the correct type. This should never happen in production use but may break tests that use mock data.

... (truncated)

Commits

• 8506690 Bump version to 6.2.0
• 6916bce Update generated code (#1024)
• 51faa13 Types for CRUDL methods on parents (#1032)
• 375fc50 Enable some pyright rules (#1031)
• 1d48f20 Pyright: fix more type suppressions (#1023)
• 2c598fb Bump version to 6.1.0
• 080f3f3 Update generated code (#1016)
• 469b3d6 Run Pyright & begin adding type annotations (#1020)
• 9ce0588 Update CHANGELOG.md
• 130e57f Update CHANGELOG.md
• 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 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)