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

Remove Laravel 4 support #123

Merged
merged 13 commits into from
Mar 18, 2018
Merged

Remove Laravel 4 support #123

merged 13 commits into from
Mar 18, 2018

Conversation

stayallive
Copy link
Collaborator

Since Laravel 4 was released in 2013 and we have a good base for support (0.8.*) we can safely drop it IMO. So this PR does this and starts testing on Laravel 5.6.

phpcs fixer was also updated to v2 because of conflicts, I am not sure on the config but we can revisit this later and sync with sentry-php.

@@ -20,7 +17,7 @@ protected function getPackageProviders($app)
protected function getPackageAliases($app)
{
return [
'Sentry' => 'Sentry\SentryLaravel\SentryFacade'
'Sentry' => 'Sentry\SentryLaravel\SentryFacade',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe you can use ::class?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No since we have to support PHP 5.4 :( (for Laravel 5.0)

composer.json Outdated
@@ -13,11 +13,11 @@
],
"require": {
"php": ">=5.3.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this modification seems to break BC, maybe you should bump to "php": "^5.6||^7.0"?
It's not ideal to have an open upper constraint...

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are correct, good one!

However I have to make this ^5.4||^7.0 since Laravel 5 works on PHP 5.4.

.travis.yml Outdated
@@ -20,11 +20,16 @@ env:
- LARAVEL=5.3.* TESTBENCH=3.3.* PHPUNIT=5.7.*
- LARAVEL=5.4.* TESTBENCH=3.4.* PHPUNIT=5.7.*
- LARAVEL=5.5.* TESTBENCH=3.5.* PHPUNIT=~6.0
- LARAVEL=5.6.* TESTBENCH=3.6.* PHPUNIT=~7.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you forced to specify the PHPUnit version too? It should be automatically chosen by Composer...

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, since composer.json specifies ^4.6.6 and the other 2 dependencies also so they need to be overwritten in the composer file which is what these do.

@dcramer
Copy link
Member

dcramer commented Feb 12, 2018

Seems fine to me (dropping support), though I would ask we document "On Laravel 4? Use version XXX".

README.md Outdated
@@ -14,6 +14,10 @@

Laravel integration for [Sentry](https://sentry.io/).

## Laravel Version Compatibility

- Laravel `4.2.x` is supported untill version `0.8.x` (`composer require "sentry/sentry-laravel:0.8.*"`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: until

composer.json Outdated
@@ -13,14 +13,14 @@
],
"require": {
"php": "^5.4||^7.0",
"illuminate/support": "^5.0",
"sentry/sentry": "^1.8"
"illuminate/support": "5.0.*|5.1.*|5.2.*|5.3.*|5.4.*|5.5.*|5.6.*",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe ^5.0, <5.7 is more readable?

@stayallive
Copy link
Collaborator Author

Fix issues with the slow failing builds thanks to @agentsib (getsentry/sentry-symfony#112)

@stayallive stayallive merged commit fe3f797 into master Mar 18, 2018
@stayallive stayallive deleted the remove-laravel-4-support branch March 18, 2018 15:45
}
} catch (Exception $e) {
error_log(sprintf('sentry.breadcrumbs error=%s', $e->getMessage()));
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any chance this should be named sentry.user_context maybe, instead of …breadcrumbs?

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

Successfully merging this pull request may close these issues.

4 participants