Since v2.15.6 there is a new task being executed after the deploy:compile_assets task, which is defined in the capistrano-rails gem:

First of all, this appears to create a very strong dependency on (capistrano-)rails which might be intended, but not something I expected.

Secondly, when I'm developing an app without assets I will not include the capistrano/rails/assets task (because it will fail) and this will, understandably, result in the following error:

Don't know how to build task 'deploy:compile_assets' (see --tasks)

Am I missing something, or should this task be conditional based on whether capistrano-rails is available and assets exist?