Skip to content

Commit

Permalink
Referencing release notes in update instructions. (#756)
Browse files Browse the repository at this point in the history
  • Loading branch information
grasmash authored Dec 6, 2016
1 parent 83e31c5 commit ee07eff
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion readme/updating-blt.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ If you are already using BLT via Composer, you can update to the latest version
# Remove deprecated files.
blt cleanup

Review and commit changes to your project files. For customized files like `.travis.yml` or `docroot/sites/default/settings.php` it is recommended that you use `git add -p` to select which specific line changes you'd like to stage and commit.
Check the [release information](https://github.com/acquia/blt/releases) to see if there are special update instructions for the new version. Review and commit changes to your project files.

On occasion, updating BLT will result in changes to your project's composer.json file. This can happen when the upstream BLT project adds new dependencies or changes the pinned version of a dependency. In cases like this, BLT will print a message alerting you to run `composer update` an additional time so that you apply the changed dependencies locally.

Expand Down

0 comments on commit ee07eff

Please sign in to comment.