Relaxing version constraints for illuminate

[mvdstam]

This enables minor version bumps, so Laravel 5.0, 5.1, 5.2, etc. (But not 6.x.x) can be used with this package.

Also see issue #395 😄

[vinkla]

Is this really a good solution? We don't know if Laravel 5.2 will break stuff. That means all current installations updating to 5.2 will break.

[GrahamCampbell]

Yeh, this commit is wrong.

[GrahamCampbell]

Allowing use with all minor versions is a bad idea, as each minor laravel release is the same as a semver major release.

[mvdstam]

So, even Laravel 5 isn't doing proper semver? That's kinda silly. Minor version bumps shouldn't break backwards compatibility, especially with frameworks. That is kind of the whole point of minor releases.

[lucadegasperi]

@GrahamCampbell The previous version of the composer.json file should be better then?

[vinkla]

@lucadegasperi Yes.

[barryvdh]

Well, the release was already tagged so it's still a problem..
https://packagist.org/packages/lucadegasperi/oauth2-server-laravel
4.0.1 will allow all 5.x versions. So people using L5.2 and requiring 4.x of your package, will be able to get 4.0.1 instead of an error that no package is available.

When a new release is made to support 5.2 (and 5.3 and 5.4 etc) it isn't a super big problem, but not really great.
Not sure if it's easy to fix by re-tagging or something. (Which usually isn't a good idea either)

[lucadegasperi]

Tagging 4.0.2 right now

[barryvdh]

Doesn't matter, the tag remains available. Composer scans all tags to find a match, so 4.0.1 will always match, even if 4.0.2 etc don't.

[GrahamCampbell]

Yeh, the 4.0.1 tag needs deleting.