Challenge 2 / 2

You run symfony composer recipe:update and it refuses because you have uncommitted changes. You really want to update recipes now without losing your work. What’s the safest move?

Clear the Symfony cache with symfony console cache:clear and then rerun the recipe update.

Run symfony composer recipe:update --force to ignore git status.

Delete composer.lock so Symfony Flex stops caring about your working tree being dirty.

Commit your current changes (or stash them), then run symfony composer recipe:update, and afterwards bring your work back if you stashed it.

Rewatch the video