Skip to content

Releases: matrix-org/mjolnir

v1.8.3

03 Oct 19:57
Compare
Choose a tag to compare

What's Changed

  • Fix default config to maintain backwards compatibility by @turt2live in #535

Full Changelog: v1.8.2...v1.8.3

v1.8.2

03 Oct 18:31
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.8.1...v1.8.2

v1.8.1

02 Oct 17:56
Compare
Choose a tag to compare

What's Changed

  • Add quote charaters to mxc match regex by @H-Shay in #532

Full Changelog: v1.8.0...v1.8.1

v1.8.0

01 Oct 22:42
Compare
Choose a tag to compare

What's Changed

  • Resolve aliases and get via servers before storing watch list by @H-Shay in #518
  • Support authenticated media (by updating bot-sdk / matrix-appservice-bridge) by @Half-Shot in #523
  • Fix NSFW protection not awaiting redaction by @Half-Shot in #526
  • Log the name of the failed protection to the moderation room when it fails. by @Half-Shot in #525
  • Add protection for mention spam by @Half-Shot in #524
  • Improve messaging and checks in NSFW protection by @H-Shay in #529
  • Add native encryption support to Mjolnir by @H-Shay in #528

Note that configuration options related to Pantalaimon are now deprecated (as native encryption is now supported in mjolnir) and will be removed at a later date.

Full Changelog: v1.7.0...v1.8.0

v1.7.0

12 Sep 15:57
Compare
Choose a tag to compare

What's Changed

New Contributors

Special Thanks

  • Thanks to @Gnuxie for inspiration/groundwork on the NSFW protection

Full Changelog: v1.6.5...v1.7.0

v1.6.5

14 Nov 22:25
v1.6.5
f270633
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.6.4...v1.6.5

v1.6.4

11 Jan 13:45
Compare
Choose a tag to compare

This is a bugfix release.

ChangeLog

Bot

  • Bugfix: In Mjölnir-for-all, make sure that config.bot.displayName is always set, by @Yoric in 9693149

v1.6.3

11 Jan 10:16
Compare
Choose a tag to compare

ChangeLog

Bot

  • Bugfix: !mjolnir config get was broken, should now be fixed by @jesopo in 5824539.
  • Feature: Support for decentralized abuse report (MSC3215). Use command !mjolnir rooms setup <room alias/ID> reporting to setup a room so that users can decide to send abuse reports to moderators (who can read the offending messages) instead of homeserver administrators (who typically cannot) by @Yoric in fa5fbee, 5b509a2. Sending an abuse report this way currently requires Element Web Develop with Labs feature report_to_moderator.
  • Feature: Mjölnir-for-all bot now has a nicer name and is easier to invite by @Yoric in d83127e.

Hosting

  • Feature: Early support for OpenMetrics/Prometheus. If you are hosting your Mjölnir, this will let you monitor e.g. CPU usage, memory usage, number of Matrix errors, ... Additional probes may be added in the future. Off by default. By @Yoric in c3cb22b

Security

v1.6.2

02 Jan 12:04
Compare
Choose a tag to compare

Changelog

Year

  • We are now in 2023. Happy New Year to all!

Bot

  • Change of behavior The bot can now start even if it doesn't manage to resolve some policy rooms. Note that this situation is not ideal, because a broken policy room means that your protections are most likely broken, but at least users are now able to use Mjölnir to fix that list by @Yoric in 433ff7e.
  • Change of behavior Setting autojoinOnlyIfManager is now true by default by @Gnuxie in 1d3da94.
  • Performance improvement Changing the policy sync algorithm means that we need fewer communications with the homeserver whenever there are policy list changes by @Gnuxie in 704bb66.

Monitoring

  • Mjölnir now supports sending events and alerts to a Sentry server by @Yoric in 2915757.

Dependencies

v1.6.1

23 Nov 11:15
Compare
Choose a tag to compare

Changelog

Bot:

  • Change of behaviour: Mjolnir now supports specifying the config file with the argument --mjolnir-config. It is highly recommended that you do this as opposed to relying on the environment variable NODE_ENV. The documentation for running with docker and from source have been updated accordingly.
  • Change of behaviour: If you had run latest since v1.5.0 or v1.6.0, briefly mjolnir would have loaded default.yaml if NODE_ENV was unset, whereas previously it would have loaded development.yaml. This led to highly confusing behaviour as the documentation for running from source had instructed users to create development.yaml without setting NODE_ENV=development while running mjolnir, which was how mjolnir understood to load development.yaml in all previous versions. Silently loading the default was an undocumented new behaviour that has now been removed.
  • Fixed a bug where if config.protectAllJoinedRooms was enabled mjolnir would temporarily start protecting all watched policy lists at startup. by @Gnuxie in #431. Thanks to @cremesk for reporting.

Full Changelog: v1.6.0...v1.6.1