Remove notifier module (#1237)

Author: clementbiron

.env.example

@@ -5,7 +5,6 @@ OTA_ENGINE_GITHUB_TOKEN=your_github_token_here
 OTA_ENGINE_GITLAB_TOKEN=your_gitlab_token_here
 OTA_ENGINE_GITLAB_RELEASES_TOKEN=your_gitlab_releases_token_here
 OTA_ENGINE_DATAGOUV_API_KEY=your_datagouv_api_key_here
-OTA_ENGINE_SENDINBLUE_API_KEY=your_sendinblue_api_key_here
 OTA_ENGINE_SMTP_PASSWORD=your_smtp_password_here
 
 HTTP_PROXY=http://proxy.example.com:8080

CHANGELOG.md

@@ -2,6 +2,15 @@
 
 All changes that impact users of this module are documented in this file, in the [Common Changelog](https://common-changelog.org) format with some additional specifications defined in the CONTRIBUTING file. This codebase adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## Unreleased [major]
+
+> Development of this release was supported by the [NGI0 Commons Fund](https://nlnet.nl/project/Modular-OTA/), a fund established by [NLnet](https://nlnet.nl/) with financial support from the European Commission's [Next Generation Internet](https://www.ngi.eu) programme, under the aegis of DG CNECT under grant agreement N°101069594.
+
+### Removed
+
+- Remove Notifier module
+- **Breaking:** Remove all default SMTP values (`host`, `port`, `username`) from logger configuration; operators enabling `sendMailOnError` must now explicitly set all three in [`@opentermsarchive/engine.logger.smtp`](https://docs.opentermsarchive.org/collections/reference/configuration/#logger)
+
 ## 10.6.1 - 2026-02-05
 
 > Development of this release was supported by [Reset Tech](https://www.reset.tech).

CONTRIBUTING.md

@@ -218,7 +218,7 @@ There are five ways to handle operational errors:
 - **Log the error — and do nothing else**. If it's a minor error and there’s nothing you can do about, and there is no reason to stop the whole process.
 - **Crash immediately**. If the error cannot be handled and can affect data integrity.
 
-In our case, we consider all `fetch`-related and `extract`-related errors as expected, so as operational errors and we handle them by logging but we do not stop the whole process. We handle errors related to the `notifier` in the same way.
+In our case, we consider all `fetch`-related and `extract`-related errors as expected, so as operational errors and we handle them by logging but we do not stop the whole process.
 In contrast, we consider errors from the `recorder` module as fatal, and we crash immediately.
 
 #### Handling programmer errors

config/default.json

@@ -42,20 +42,9 @@
       "language": "en"
     },
     "logger": {
-      "smtp": {
-        "host": "smtp-relay.brevo.com",
-        "port": 587,
-        "username": "admin@opentermsarchive.org"
-      },
       "sendMailOnError": false,
       "timestampPrefix": true
     },
-    "notifier": {
-      "sendInBlue": {
-        "updatesListId": 850,
-        "updateTemplateId": 7
-      }
-    },
     "dataset": {
       "publishingSchedule": "30 8 * * MON"
     }

package-lock.json

@@ -95,7 +95,6 @@
     "puppeteer": "^24.22.0",
     "puppeteer-extra": "^3.3.6",
     "puppeteer-extra-plugin-stealth": "^2.11.2",
-    "sib-api-v3-sdk": "^8.5.0",
     "simple-git": "^3.28.0",
     "swagger-jsdoc": "^6.2.8",
     "swagger-ui-express": "^5.0.1",