Make Maintenance > Update easier to follow - it opens with where the install stands (up to date, an update available, updating, the database still to finish, checking) and the one button for it, Update ITFlow in place of Queue Update, with what's new below it (the release notes between this install and the latest, read from the changelog by the update check, developer notes and commits folded away), what to do first including the ITFlow files changed on this install that updating would put back, the update shown running with the page refreshing itself and then when it finished or what stopped it, and this install's version, branch, database, commit, last check, last update, cron and the command to update from a shell alongside; database 3.5.7 adds settings.config_update_details, written by cron/update_check.php through the new updateCheckDetails(), updateChangelogSections() and updateChangelogHtml() render the release notes escaped, cron/app_update.php asks for a fresh check after an update, changelog updated

css/itflow_custom.css

@@ -9287,3 +9287,10 @@ a.itflow-portal-request:focus-visible {
         width: 460px;
     }
 }
+
+/* A shell command to copy (Maintenance > Update) - its lines kept, a long path wrapped
+   rather than scrolled out of sight */
+.itflow-command {
+    white-space: pre-wrap;
+    word-break: break-all;
+}