Adding a comment explaning when changes need to be pushed to the bot'…

…s PR.

release.md

@@ -188,7 +188,7 @@ Note: make sure when you do this that you're in a virtualenv, your current worki
 A couple of hours after you publish the GitHub release, a bot will open a PR to our [feedstock](https://github.com/conda-forge/evalml-core-feedstock) that automatically
 bumps the recipe to use the latest version of the package.
 
-If you had to modify the recipe in Step 1, then make those changes and push to the bot's PR. For help on how to push changes to the
+If you had to modify the recipe in Step 1 (most common case is when dependencies are updated), then make those changes and push to the bot's PR. For help on how to push changes to the
 bot's PR please read this [document.](https://conda-forge.org/docs/maintainer/updating_pkgs.html#pushing-to-regro-cf-autotick-bot-branch)
 If you did not have to modify the recipe in Step 1, the bot's PR should be good to merge as-is.
 In either case, wait for the CI tests to pass before merging.