-
Notifications
You must be signed in to change notification settings - Fork 850
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
Drop support for PHP 5.3 #410
Conversation
@@ -60,6 +60,12 @@ Please see https://stripe.com/docs/api for up-to-date documentation. | |||
|
|||
## Legacy Version Support | |||
|
|||
### PHP 5.3 | |||
|
|||
If you are using PHP 5.3, you can download v5.8.0 ([zip](https://github.com/stripe/stripe-php/archive/v5.8.0.zip), [tar.gz](https://github.com/stripe/stripe-php/archive/v5.8.0.tar.gz)) from our [releases page](https://github.com/stripe/stripe-php/releases). This version will continue to work with new versions of the Stripe API for all common uses. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth adding a scary blurb about how bad using this version (and 5.2) is?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't hurt!
- STRIPE_MOCK_VERSION=0.5.0 | ||
matrix: | ||
- AUTOLOAD=1 | ||
- AUTOLOAD=0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for changing this whole thing back :)
LGTM. |
How about the short array syntax in PHP 5.4 ? |
@arcanedev-maroc Yep, that's on my TODO list too! :) |
r? @brandur-stripe
cc @stripe/api-libraries
This PR drops support for PHP 5.3, and gets rid of some now unneeded stuff.
Note that the destination branch is
integration-v6
instead ofmaster
so that we can merge all PRs going into stripe-php 6.0.0 and solve conflicts before merging intomaster
.Fixes #406, although the fix won't be effective until we merge into
master
and actually release a new major version.