Fix: PostgreSQL 16 Upgrade - Fails in some configurations

We have resolved an issue where in some environments, the PostgreSQL 16 upgrade may fail with a “No space left on device” error.

Fix: Upgrade Script - Improved license detection during upgrade

In some cases, the upgrade script did not correctly detect an existing license. This has been improved to ensure licenses are reliably recognized during upgrades.

Improved handling of Java 21 upgrades on supported Linux distributions.
Enhanced validation and dependency checks to better detect package conflicts during the upgrade process.

Resolved an issue where opening server charts shortly after adding a server to an impact set could cause the charts panel to become unresponsive in some application map scenarios.

Improved consistency in the Server Properties view so CPU, memory, and storage details are now displayed correctly on Windows-based servers, aligning the experience with Linux servers.

Fixed an issue where interval time changes in Software & CVE Discovery settings were not reflected in the Scheduler at some cases.

Notifications - Summary Report scheduling reliability

Fixed an issue where saving a Summary Report did not persist the selected days of the week, and enabling the report via the toggle did not immediately trigger it at some cases.

​Scheduler - Interval selection now applies correctly

Fixed an issue where selecting Daily or Weekly intervals was still treated as a custom interval.

Improved the upgrade flow for AWS EC2 deployments to better handle Java and database upgrades. Resolved an issue where Tomcat could fail to start due to an incorrect JAVA_HOME configuration, and enhanced validation and logging to prevent similar upgrade issues in future versions.

Resolved an issue where CSV imports for Server Tag lists completed successfully but the imported values were not searchable or usable at some cases.