Spring v1.1.0 Release Notes

    • A bin/spring binstub is now generated. This allows us to load spring correctly if you have it installed locally with a BUNDLE_PATH, so it's no longer necessary to install spring system-wide. We also activate the correct version from your Gemfile.lock. Note that you still can't have spring in your Gemfile as a git repository or local path; it must be a proper gem.
    • Various changes to how springified binstubs are implemented. Existing binstubs will continue to work, but it's recommended to run spring binstub again to upgrade them to the new format.
    • ๐Ÿšš spring binstub --remove option added for removing spring from binstubs. This won't work unless you have upgraded your binstubs to the new format.
    • config/database.yml is watched
    • ๐Ÿ‘ Better application restarts - if you introduce an error, for example by editing config/application.rb, spring will now continue to watch your files and will immediately try to restart the application when you edit config/application.rb again (hopefully to correct the error). This means that by the time you come to run a command the application may well already be running.
    • Gemfile changes are now gracefully handled. Previously they would cause spring to simply quit, meaning that you'd incur the full startup penalty on the next run. Now spring doesn't quit, and will try to load up your new bundle in the background.
    • ๐Ÿ›  Fix support for using spring with Rails engines/plugins