Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency stripe to v12 #771

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 20, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
stripe ^11.7.0 -> ^12.0.0 age adoption passing confidence

Release Notes

stripe/stripe-node

v12.0.0

Compare Source

  • #​1743 Remove Stripe.default and Stripe.Stripe
    This was added to maintain backwards compatibility during the transition of stripe-node to a dual ES module / CommonJS package, and should not be functionally necessary.

  • #​1742 Pin latest API version as the default
    ⚠️ ACTION REQUIRED: the breaking change in this release likely affects you ⚠️

    In this release, Stripe API Version 2022-11-15 (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-node v12, you must either

    1. (Recommended) Upgrade your integration to be compatible with API Version 2022-11-15.

      Please read the API Changelog carefully for each API Version from 2022-11-15 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 2022-11-15 when initializing stripe-node.

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

      - const stripe = require('stripe')('sk_test_...');
      + const stripe = require('stripe')('sk_test_...', {
      +   apiVersion: 'YYYY-MM-DD' // Determine your default version from https://dashboard.stripe.com/developers
      + })

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


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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependency label Apr 20, 2023
@changeset-bot
Copy link

changeset-bot bot commented Apr 20, 2023

⚠️ No Changeset found

Latest commit: 978d49c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Apr 20, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 20, 2023 8:44pm
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 20, 2023 8:44pm
storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 20, 2023 8:44pm
www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 20, 2023 8:44pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants