Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Followup from #184418: update(_status) results stale for up to 6 hours. The one edge case that doesn't yet solve is when release nodes are manually published or unpublished. For example, if the security team publishes a release node once an SA goes out, or if they decide to unpublish releases in response to a vulnerability report or something. In those cases, the Update status results will still be stale for up to 6 hours, unless the sec team manually regenerates the release history files for the affected projects (which is now a lot easier to do thanks to the command-line arg you can pass to project-release-create-history.php to restrict to a single project).
In #184418 there was talk of some kind of dirty bit in {project_release_nodes}, and a mode of invoking project-release-create-history.php that just queries for release nodes with the dirty bit set, regenerates the history, then clears the bit. Not sure what else to do, but if anyone has any bright ideas, I'm all ears.
Comments
Comment #1
jason_purdy commentedThat fixed it, thanks! I had to manually run the check ( /admin/reports/updates/check), but after that ran, everything was up-to-date and no security alerts. :)
Thanks again!
Comment #2
jason_purdy commentedOops, I'm so sorry, I posted this in the wrong queue and updated the status. I'm changing it back to 'active'.
Comment #3
avpadernoI am closing this issue, as Drupal 6 is no longer supported. Feel free to re-open it if the bug is still present in the Drupal 7 version of the module.