- Issue created by @ivnish
- 🇺🇸United States cmlara
Speaking as a dev who targeted D8+ while other devs were responsible for the D7 releases:
Some contrib issues never were assigned to D8 releases and only existed in D7 branches. After EOL I went through my modules issue by issue and migrating several still relevant into the active release branch.
It would seem treasonable to suspect similar to exist across the ecosystem which makes closing contrib issues far more questionable.
If contrib issues were to be closed I highly recommend they be given a unique issue tag so that a future developer can easily query them without needing to sort through unrelated issues.
- ivnish Kazakhstan
I think the best way will be VBO with action "Close selected issues with auto text" and text from 📌 Bulk update Drupal core 7.x issues after Drupal 7 EOL Active
Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.
But VBO in drupal.org is a dream :)