v1.30.0

[minor]

• Improved RPKI alerting to include more detailed information about the exact expiring/malfunctioning components. It will tell you whether your ROAs are expiring or something else in the validation chain (thanks to rpki-client metadata, @job). E.g.,

  The following ROAs will become invalid in less than 2 hours: <193.0.0.0/21, 3333, 21, ripe>; 
  <193.0.10.0/23, 3333, 23, ripe>. The reason is the expiration of the following 
  parent components: rpki.ripe.net/repository/aca/KpSo3VVK5wEHIJnHC2QHVV3d5mk.cer
  

• Improved alert metadata to include info about the exact ROAs covering the prefix at the time of the reporting, the validator used, the host used for the validation, the time of the last validation cycle, and more.
• Improved logs to inform when and where alerts are sent (to which email/ip/channel), in addition to the usual log in case of failure. This helps in discovering silent failures (e.g., a fw between BGPalerter and your syslog instance).
• Split channels between monitorRPKI and monitorROAs in the default configuration, to easily dispatch the alerts in different reports.
• Added support for docker-compose (thanks @GoliathLabs).

[patch]

• Updated dependencies and improved security.
• Fixed error in generating context when showPath is active but no paths are reported.
• Fixed error on neighbor auto-config on configurations when generating configurations based only on prefixes (reported by @donwito).
• Improved performance on watching prefix list.
• Fixed canary feature not recovering after multiple failures.
• Improved documentation about installation and ROA alerting.
• Updated version of supported Kafka.
• Improved linux doc on how to automatically run upgrades (thanks @herbetom).
• Reduced memory usage of prefix-generation phase.
• Many minor fixes...