- Issue created by @wangshy
- Status changed to Closed: won't fix
12 days ago 8:38am 14 October 2025
content_lock_post_update_uninstall_content_lock_timeout is intended to deprecate content_lock_timeout. The problem is it won't work if sites use "drush deploy" for CI.:
https://www.drush.org/12.x/deploycommand/
drush updatedb --no-cache-clear
drush cache:rebuild
drush config:import
drush cache:rebuild
drush deploy:hookThe post update is run at the first step then gets reverted back by drush cim.
Place the logic in HOOK_deploy_NAME() instead of post_update hook
Though deploy hook is from drush not core, it's unlikely any Drupal site does not use drush, and it'd trigger error if so that is better than an undetectable failure.
Active
3.0
Code