v1.6.1
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 variableNODE_ENV
. The documentation for running with docker and from source have been updated accordingly. - Change of behaviour: If you had run
latest
sincev1.5.0
orv1.6.0
, briefly mjolnir would have loadeddefault.yaml
ifNODE_ENV
was unset, whereas previously it would have loadeddevelopment.yaml
. This led to highly confusing behaviour as the documentation for running from source had instructed users to createdevelopment.yaml
without settingNODE_ENV=development
while running mjolnir, which was how mjolnir understood to loaddevelopment.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