Document composer sync recipe force option #14001
Conversation
|
|
||
| .. code-block:: terminal | ||
|
|
||
| $ composer sync-recipes --force |
There was a problem hiding this comment.
We should recommend this command composer recipes:install vendor/package --force -v to update one by one and -v for more information about the update
There was a problem hiding this comment.
@maxhelias yes i see your idea
but as the upper code is a full composer update, that is why i added here a full "recipes update"
the -v option can be added indeed :)
There was a problem hiding this comment.
So just composer recipes:install --force -v will have the same behavior
|
Hi @noniagriconomie! I'm a bit unsure about how I missed this PR when merging #13320 . To me, it seems like the changes in this PR would add duplicate information the upgrade guides now that the other PR is merged. Is there anything left to do in this PR, or should it be closed? Again, sorry for loosing your changes and thanks a lot for the time you've spent to improve the docs for everyone! |
|
@wouterj no worry, the main goal was to properly document the process of updating the recipes just to be precise, i just think in a doc part of "Upgrading/Updating Recipes" Feel free to close this one if the wording is ok |
|
I agree with Wouter and that's why we're closing this without merging. Please, note that this RST file is included just before the other RST that explains the update of recipes (https://github.com/symfony/symfony-docs/blob/5.x/setup/_update_recipes.rst.inc) and which talks about So, this RST file is included in other articles which don't include the "_update_recipes.rst.inc", but that's fine because it's about updating patch/minor Symfony versions. Thanks for understanding! |
Small improvement on the upgrade packages process
It may help the process of upgrading/reinstalling to get latest recipe code
Also fix #12698 👍
edit: maybe check also #13320 as it is very similar :)