@@ -4,6 +4,73 @@ Please make sure to always read our [Upgrading](doc/80-Upgrading.md) documentati
44
55## What's New
66
7+ ### What's New in Version 2.12.0
8+
9+ You can find all issues related to this release on our [ Roadmap] ( https://github.com/Icinga/icingaweb2/milestone/79?closed=1 ) .
10+
11+ #### PHP 8.2 Support
12+
13+ This release finally adds support for the latest version of PHP, 8.2. This means that installations on Debian Bookworm,
14+ Ubuntu 23.10 and Fedora 38+ can now install Icinga Web without worrying about PHP related incompatibilities. Some of our
15+ other modules still require an update, which they will receive in the coming weeks. Next week Icinga DB Web will follow.
16+ Icinga Certificate Monitoring, Icinga Business Process Modeling and Icinga Reporting the weeks after.
17+
18+ * Support for PHP 8.2 [ #4918 ] ( https://github.com/Icinga/icingaweb2/issues/4918 )
19+
20+ #### Simplified Database Migrations
21+
22+ Anyone who already performed an upgrade of Icinga Web or some Icinga Web module in the past has done it: A database
23+ schema upgrade. This usually involved the following steps:
24+
25+ * Knowing that a database might need an upgrade
26+ * Figuring out if that's true, by checking the upgrade documentation
27+ * Alternatively relying on the users to find out about it as they're running into database errors
28+ * Locating the upgrade file
29+ * Connecting to the machine the database is running on
30+ * Transferring the upgrade file over
31+ * Importing the upgrade file into the correct database
32+
33+ With Icinga Web v2.12 and later, upgrade the application and, yes, still check the upgrade documentation. That's still
34+ mandatory! But if you notice there, that just a database upgrade is necessary you can simply log in and check the
35+ * Migrations* section in the * System* menu. With a single additional click you can perform the database upgrade directly
36+ in the UI then. This view also offers to migrate module databases. The earlier mentioned updates of Icinga Certificate
37+ Monitoring and Icinga Reporting will pop up there once they arrive.
38+
39+ * Provide a way to easily perform database migrations [ #5043 ] ( https://github.com/Icinga/icingaweb2/issues/5043 )
40+
41+ #### Content-Security-Policy Conformance
42+
43+ Err, what? That's an HTTP header to prevent cross site scripting attacks. (XSS) Still confused? It's a technique
44+ to stop bad individuals. A very effective technique even. You don't need to do anything, other than visiting the
45+ general configuration of Icinga Web and enabling the respective setting. The only downer here, is that support
46+ for it isn't as widespread yet as you might hope. Icinga Web itself of course has it, but not all modules. But don't
47+ worry, you might have guessed it already, those are the same modules which will receive updates in the coming weeks.
48+
49+ * Support for Content-Security-Policy [ #4528 ] ( https://github.com/Icinga/icingaweb2/issues/4528 )
50+
51+ #### Other Notable Changes
52+
53+ There are not only such big changes as previously mentioned part of this release.
54+
55+ Some module developers may be happy to hear that there is now more control for the server over the UI possible.
56+ And with a new Javascript event it is now possible to react upon a column's content being moved to another column.
57+ Now built-in into the framework is also an easy way to mark content in the UI as being copiable with a single click
58+ by the user.
59+
60+ * Allow to initiate a refresh with ` __REFRESH__ ` [ #5108 ] ( https://github.com/Icinga/icingaweb2/pull/5108 )
61+ * Don't refresh twice upon ` __CLOSE__ ` [ #5106 ] ( https://github.com/Icinga/icingaweb2/pull/5106 )
62+ * Add event ` column-moved ` [ #5049 ] ( https://github.com/Icinga/icingaweb2/pull/5049 )
63+ * Add copy-to-clipboard behavior [ #5041 ] ( https://github.com/Icinga/icingaweb2/pull/5041 )
64+
65+ Then there are some fixes related to other integrations. It is now possible to set up resources for Oracle databases,
66+ without a ` host ` setting, which facilitate dynamic host name resolution. A part of the ` monitoring ` module's integration
67+ into the Icinga Certificate Monitoring prevents a crash of its collector daemon in case the connection to the IDO was
68+ interrupted. And exported content, with data that has double quotes, to CSV is now correctly escaped.
69+
70+ * Access Oracle Database via tnsnames.ora / LDAP Naming Services [ #5062 ] ( https://github.com/Icinga/icingaweb2/issues/5062 )
71+ * Reduce risk of crashing the x509 collector daemon [ #5115 ] ( https://github.com/Icinga/icingaweb2/pull/5115 )
72+ * CSV export does not escape double quotes [ #4910 ] ( https://github.com/Icinga/icingaweb2/issues/4910 )
73+
774### What's New in Version 2.11.4
875
976You can find all issues related to this release on our [ Roadmap] ( https://github.com/Icinga/icingaweb2/milestone/78?closed=1 ) .
0 commit comments