Problem/Motivation
Drupal 10 no longer checks for older updates that start with a number lower than minimum supported core. eg Since 2.0.x branch minimum version is 9.1, updates starting with 8NNN are no longer run. That means updates 8001 and 8002 can now be safely removed as they should have run.
However, there is the slight possibility that update 8002 might be missed.
Proposed resolution
- Remove updates 8001 and 8002.
- Let drupal know that they have been removed, but only up to 8001 since 8002 could possibly be missed.
- Add post_update which does the same thing as 8002 but guards against overriding permissions set by admin
Remaining tasks
- ✅ File an issue
- ✅ Addition/Change/Update/Fix
- ✅ Release notes snippet
- ❌ Release
Release notes snippet
Issue fork cas_server-3465846
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #4
elc commentedThis needs to be merged into 2.0.x as it suffers the same issue when run on a Drupal 10 site.
Comment #7
elc commentedComment #8
elc commentedOn review, the number set in
hook_update_last_removed()should be 8002, as the replacement is no longer an hook_update_NNNN, but rather a post_update.Comment #11
elc commentedNumber corrected.