Added workaround for magento/magento2#6437

Author: davidalger

CHANGELOG.md

@@ -6,6 +6,7 @@ UNRELEASED
 * Added ability to only deploy specific themes via the new `:magento_deploy_themes` array
 * Added `:magento_deploy_confim` setting which requires user confirmation of deployment to specific capistrano stages
 * Added call to pre-generate secure RequireJS config (issue #21)
+* Added workaround for Magento 2.1 specific bug where lack of a deployed_version.txt file would fail static asset deploy
 * Updated formatting of pending deployment messaging
 * Updated composer calls to specify --no-dev and --optimize-autoloader when `:magento_deploy_production` is not set (issue #22, #23)
 * Fixed bug causing maintenance mode to be enabled on deploy even when `:magento_deploy_maintenance` was set to false

lib/capistrano/tasks/magento.rake

@@ -190,6 +190,10 @@ namespace :magento do
           # Output is being checked for a success message because this command may easily fail due to customizations
           # and 2.0.x CLI commands do not return error exit codes on failure. See magento/magento2#3060 for details.
           within release_path do
+
+            # Workaround for 2.1 specific issue: https://github.com/magento/magento2/pull/6437
+            execute "touch #{release_path}/pub/static/deployed_version.txt"
+
             output = capture :magento,
               "setup:static-content:deploy #{deploy_languages}#{deploy_themes} | stdbuf -o0 tr -d .",
               verbosity: Logger::INFO