Now that the security team can specifically mark releases insecure
The update module could determine if a project is secure even if there is security release in a new release. Even in cases where the latest release of a project is security release it does not automatically mean that all previous releases will be marked as insecure.
For example a hypothetical core scenario:
8.100.2 would be marked as "insecure" but 8.100.1 might not be marked as insecure because the problem code wasn't in it. For sites running 8.100.1 that would not be required to update to be secure.
Depend on XML from drupal.org to determine if a release is insecure and if a security update is required.
Not seeing a "Security update required!" message if not needed.
Possibly none, possible changes or removal of dead code related to the old method of determining security status.
Instead of computing if a release is secure or not based on if a newer release includes security fixes, rely on a secure vs. insecure flag in the update status XML data.
Needs work
10.1 ✨
Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
Still needs usability review.
Will post to the slack channel.
Meantime can MR be updated for 10.1 please.