Release 0.2.0 (#428)

Author: nilmerg

.mailmap

@@ -1,5 +1,8 @@
 Alexander A. Klimov <[email protected]> <[email protected]>
 Alexander A. Klimov <[email protected]> <[email protected]>
+Bastian Lederer <[email protected]> <[email protected]>
+Jan Schuppik <[email protected]> <[email protected]>
+Johannes Rauh <[email protected]> <[email protected]>
 Noé Costa <[email protected]> <[email protected]>
 Ravi Kumar Kempapura Srinivasa <[email protected]> <[email protected]>
 Ravi Kumar Kempapura Srinivasa <[email protected]> <[email protected]>

AUTHORS

@@ -1,7 +1,11 @@
 Alexander A. Klimov <[email protected]>
 Alvar Penning <[email protected]>
+Bastian Lederer <[email protected]>
 Florian Strohmaier <[email protected]>
+Jan Schuppik <[email protected]>
 Johannes Meyer <[email protected]>
+Johannes Rauh <[email protected]>
+Julian Brost <[email protected]>
 Noé Costa <[email protected]>
 Ravi Kumar Kempapura Srinivasa <[email protected]>
 Sukhwinder Dhillon <[email protected]>

CHANGELOG.md

@@ -0,0 +1,33 @@
+# Icinga Notifications Web Changelog
+
+Please make sure to always read our [Upgrading](https://icinga.com/docs/icinga-notifications-web/latest/doc/05-Upgrading/)
+documentation before switching to a new version.
+
+## 0.2.0 (2025-11-19)
+
+With Icinga Notifications 0.2.0 we changed how event rule filters are configured and processed.
+Sources are now responsible for deciding which event rules apply to a given event. In the case
+of Icinga 2, this allows associating event rules with custom variables, for example. Please
+make sure to upgrade Icinga DB to 1.5.0 and Icinga DB Web to 1.3.0 to facilitate this change.
+
+## Additional Features
+
+Some of you asked for this in the past, and now Icinga Notifications Web provides a way to configure
+contacts and contact groups using a REST API! But that's not all, the API is also thoroughly documented
+using the OpenAPI standard to make it easy to integrate with other tools. Make sure to check it out:
+https://icinga.com/docs/icinga-notifications-web/latest/doc/20-REST-API/
+
+The schedule configuration got also a highly expected enhancement: Timezone support!
+You can now configure a schedule to use a specific timezone other than the local timezone.
+When viewing a schedule, you can temporarily switch to any other timezone, allowing you to
+easily verify availability even if abroad.
+
+### Fixes and Enhancements
+
+A few months ago, we performed several user testing sessions, and this release includes the changes
+suggested during those sessions. Expect to see various small improvements and better user experience.
+The schedule configuration in particular has been improved in many ways.
+
+## 0.1.0 (2024-07-24)
+
+Initial release

doc/02-Installation.md.d/From-Source.md

@@ -13,7 +13,7 @@ Make sure you use `notifications` as the module name. The following requirements
   or [PostgreSQL](https://www.php.net/manual/en/ref.pdo-pgsql.php) PDO PHP libraries
 - [Icinga Notifications](https://github.com/Icinga/icinga-notifications)
 - [Icinga Web](https://github.com/Icinga/icingaweb2) (≥2.12)
-- [Icinga PHP Library (ipl)](https://github.com/Icinga/icinga-php-library) (≥0.17.1)
-- [Icinga PHP Thirdparty](https://github.com/Icinga/icinga-php-thirdparty) (≥0.13.0)
+- [Icinga PHP Library (ipl)](https://github.com/Icinga/icinga-php-library) (≥0.18)
+- [Icinga PHP Thirdparty](https://github.com/Icinga/icinga-php-thirdparty) (≥0.14)
 
 <!-- {% include "02-Installation.md" %} -->

doc/05-Upgrading.md

@@ -0,0 +1,35 @@
+# Upgrading Icinga DB Web
+
+Specific version upgrades are described below. Please note that version upgrades are incremental.
+If you are upgrading across multiple versions, make sure to follow the steps for each of them.
+
+## Upgrading to Icinga Notifications Web 0.2.0
+
+With Icinga Notifications 0.2.0 we changed how event rule filters are configured and processed.
+Previously, event rules could be associated with specific objects by referencing their tags.
+This is no longer the case, and how event rules are associated with objects is now fully controlled
+by the source bound to the event rule. This means each event rule must now be bound to a specific
+source, which is responsible for evaluating which objects the event rule applies to. By following
+the upgrading steps of Icinga Notifications 0.2.0, all your event rules have automatically been
+migrated and are now bound to the Icinga 2 source that is already configured. If you have filters
+configured for event rules, they need to be migrated manually though. You need to access the database
+directly for this and update it accordingly.
+
+Review the currently configured event rules and their filters:
+
+```sql
+SELECT name, object_filter FROM rule;
+```
+
+Take note of the `object_filter` values for each event rule. Store them somewhere. If you want to
+migrate them, you can do this only in the UI. In the case of Icinga 2, the supported filter syntax is
+the same as in Icinga DB Web and supports the same columns as restrictions do there. `hostgroup/…`
+becomes `hostgroup.name=…` and `servicegroup/…` becomes `servicegroup.name=…`.
+
+To migrate the filters in the UI, you need to update the table first:
+
+```sql
+UPDATE rule SET object_filter = NULL;
+```
+
+Now, you can re-apply the filters in the UI.

module.info

@@ -1,6 +1,6 @@
 Module: notifications
-Version: 0.1.0
+Version: 0.2.0
 Requires:
-  Libraries: icinga-php-library (>=0.17.1), icinga-php-thirdparty (>=0.13.0)
+  Libraries: icinga-php-library (>=0.18.0), icinga-php-thirdparty (>=0.14.0)
 Description: Icinga Notifications Web
  Manage incidents and who gets notified about them how and when