Update composer.json

[Dylan-DPC-zz]

Laravel doesn't follow semver. So having ^5.x, 5.* or >=5.x will mean that composer will install a future version even though that version breaks the package.

[mikebronner]

Hi @Dylan-DPC, thanks for the PR! At this point I am leaning to not specify the Laravel minor version, knowing that Laravel does not respect semver. My initial thinking is that between using the cache and serviceprovider functionalities provided in the two dependencies, the chances of the functionality having breaking changes are small. And if they do occur it will be something that will be easily fixed.

On the other hand, if we do implement the minor version checks in composer.json, we will be bound to push un update every 6 months, and if we don't do it within a reasonable amount of time, people who do upgrade Laravel will not be able to use this package until we do.

Hence my thinking is that it will be less maintenance to not worry about versioning problems, until there actually is a problem. :) I'm keeping this open though, while I think on this over the next few days. :)

Thanks again!

[mikebronner]

See conversation.

[mikebronner]

I've been mulling this over and am leaning toward accepting your PR. Give me a few more days, I'll work on it over the weekend. :) Thanks!