-
Notifications
You must be signed in to change notification settings - Fork 417
Conversation
I'll leave this open so other people can use it if they want a temporary workaround: {
"repositories": [
{
"type": "vcs",
"url": "https://github.com/PheRum/laravel-breadcrumbs.git"
}
],
"require": {
"davejamesmiller/laravel-breadcrumbs": "dev-master"
}
} However, I probably won't be merging it because I don't generally support multiple Laravel versions in a single Breadcrumbs version - mainly because I haven't figured out a way to run the unit tests against both/all versions. i.e. at the moment this will only run the tests against Laravel 5.6 not 5.7, while if you upgraded I will aim to release a new version with official 5.7 support in the next couple of weeks. There are some architectural changes I'm thinking of making at the same time... Cheers |
Here's how I run tests against both L5.6 and L5.7: https://github.com/spatie/laravel-view-components/blob/master/.travis.yml#L7-L14 . Works great! There are no changes needed to support L5.7 in your package, only the constraints need to be a bit more flexible. For 99% of my packages I only had to tag on extra version for If you want I could send a PR for all these changes. In my opinion you'd have no risk for adding these changes to laravel-breadcrumbs. Many users of your package could just upgrade normally to L5.7. (No need to keep in the back of your mind that you'll need to remove that Everybody runs their packages in the way they want, so if you stick with not tagging the current version for L5.7, I'd respect that. Thanks for all your excellent work with this package. I'm using it in Oh Dear!. |
Thanks Freek, I'll experiment with that. 8-) |
Let me know if you have any questions around this! |
OK, that's done and tagged as 5.1.1. Thanks again for the suggestion @freekmurze. I used the same idea but with explicit version numbers instead of (In case anyone wonders why I named the variable |
Job well done 👍 |
No description provided.