Update stripe to the latest version 🚀 #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 6.1.0 just got published.Update to this version instead 🚀 Release Notesstripe-node v6.1.0
CommitsThe new version differs by 9 commits.
See the full diff |
Version 6.1.1 just got published.Update to this version instead 🚀 Release Notesstripe-node v6.1.1
|
Version 6.2.0 just got published.Update to this version instead 🚀 Release Notesstripe-node v6.2.0
|
Version 6.2.1 just got published.Update to this version instead 🚀 Release Notesstripe-node v6.2.1
|
Version 6.3.0 just got published.Update to this version instead 🚀 Release Notesstripe-node v6.3.0
CommitsThe new version differs by 17 commits.
There are 17 commits in total. See the full diff |
Version 6.4.0 just got published.Update to this version instead 🚀 Release Notesstripe-node v6.4.0
|
Version 6.5.0 just got published. |
Version 6.6.0 just got published.Update to this version instead 🚀 Release Notesstripe-node v6.6.0
|
Version 6.7.0 just got published.Update to this version instead 🚀 Release Notesstripe-node v6.7.0
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 6.0.0 of stripe was just published.
stripeThe version 6.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of stripe.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
stripe-node v6.0.0createso that it correctly passes all arguments (this is a very minor breaking change)See the changelog for more details.
Commits
The new version differs by 4 commits.
0a5fcdaBump version to 6.0.0e48b9f7Merge pull request #453 from stripe/jlomas-fix-usage-recordsf6abc86Switch to approach similar to Application Fee Refunds654c723Fix UsageRecords so it passes through the rest of the argumentsSee the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴