Version 3.15.8.966

27 July 2026

Bug Fixes

• Database changes were skipped when updating on Linux and Docker — Fixed updates on Linux and Docker installations reporting success without applying the database changes that came with them. Anything relying on a new table or column then failed or behaved as though the feature had not been installed, and every later update repeated the problem, so a panel could fall several versions behind on its database while looking perfectly up to date. Updating to this version applies everything that was missed — as always, TCAdmin backs the database up first. Docker containers were also still running the tca command-line tool they were first installed with, so each update ran the original update steps rather than the ones shipped since; a container now picks up its updated tool the next time it starts.
• Plugin repository announcements repeating — Fixed the announcement about new and updated plugins reappearing over and over for a repository that had received nothing new. TCAdmin now announces only when the repository itself has actually changed and at least one plugin in it is still missing or out of date on your panel, so a pending update you have chosen not to install stops nagging you every hour, and clearing an announcement no longer brings it straight back on the next sync. Adding a repository no longer announces everything already in it, updated configurations on the V2 forum repository are now included as well — previously only brand-new ones were — and an announcement now lists the most recently changed plugins rather than the first few alphabetically. Turning a repository's Update notifications switch back on surfaces whatever is pending at that moment instead of staying quiet about everything that arrived while it was off.
• Create service page showed outdated variable settings — Fixed the configuration questions on the Create New Service page being shown as they looked when the blueprint's config file was last saved. Renaming a variable, rewording its description or editing its list of choices afterwards did not appear here, so whoever created the service saw the old wording and the old options — while the very same form on an existing service's Configuration page showed the current ones. Those questions are now built from the blueprint's current variables, questions belonging to a variable that no longer exists or that the signed-in user's roles do not allow are left out, and the config files load together instead of one after another, so the step opens faster.
• Dismissing a finished update was recorded in the activity log — Clearing the finished-update message on the System Update page no longer adds an entry to the activity log. Starting an update and retrying a server that failed are still recorded.