-
-
Notifications
You must be signed in to change notification settings - Fork 195
Allowing specific recipes to be "re-installed" #583
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
Conversation
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.
That's great! 👌
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.
There is one thing that we need to check, it's the symfony.lock file: does it update the version hash of the listed recipes only or for all recipes?
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.
does it update the version hash of the listed recipes only or for all recipes?
I just verified: all good, only the updated recipes are changed in the symfony.lock
This is ready to go |
Thank you @weaverryan. |
This PR was merged into the 1.5-dev branch. Discussion ---------- Allowing specific recipes to be "re-installed" Hi! Very simple: you can now re-install/update just one (or specific) recipes: ``` composer symfony:sync-recipes symfony/console --force ``` That's very helpful, as there are a few specific recipes (this is one of them) that really *do* need to be "updated", at the very least, when upgrading to Symfony 5 (as some important files have evolved over time). This relates to #575 (will help with upgrading), #518 and should go along with the PRs #562 and #565 Thanks! Commits ------- a9dad87 Allowing specific recipes to be "re-installed"
Hi!
Very simple: you can now re-install/update just one (or specific) recipes:
That's very helpful, as there are a few specific recipes (this is one of them) that really do need to be "updated", at the very least, when upgrading to Symfony 5 (as some important files have evolved over time).
This relates to #575 (will help with upgrading), #518 and should go along with the PRs #562 and #565
Thanks!