Description of the need
When looking at the available updates page it is not easy to see the date of the release and to know if there are commits that have not yet been rolled into a release. Sometimes the date of the release may be superseded by several commits and the release may be as much as two years behind the latest commits. Knowing this might help site builders and developers to solve problems more quickly and build on the work already done by others by testing if the latest commits solve the problem or not.
Likewise when browsing new modules to install, clicking on the module name will show the date of the release but shows no indication if there are commits that supersede this.
Proposed solution
Drupal, while it does not show them on the available updates page unless you have a dev version installed, does show on the project page both the latest release with date and the dev branch with the latest date.
Alternatives that have been considered
Improving the display of available updates in this way has been proposed in Drupal issue queue but has not gained traction.
I am not aware of a Drupal or Backdrop contributed module that accomplishes this.
Additional information
Attached is a screenshot from Drupal when a dev version of a module is used.
Draft of feature description for Press Release (1 paragraph at most)
Backdrop now includes information on the date of the release and the date of the latest commit in the development branch on both the available updates page and on the list of modules available to install to help site builders and developers see work that has been committed since the date of the release that may solve problems they encounter.
Recent comments
Re PHP 8.5 compatibility: not ready yet for review, but tests are passing now. So, still work in progress with issue #7008.
November 20th 2025 Weekly Meetings
This issue in the API module is blocking any upgrade of docs.backdropcms.org to later PHP versions. I had a look but not sure how this can be fixed: https://github.com/backdrop-contrib...
November 20th 2025 Weekly Meetings
The number of questions about lost configurations support my argument. Who knows how many developers use version control systems... UPDATE: The option to store in a database was added...
I need to understand how active and staging folders work – configuration management