v1.80.0

Pre-release strategy:

For the foreseeable future I'm planning a series of pre-releases as I head towards v2.0.0. The reason being there are a number of breaking changes since the last pre-fork version of Mjolnir and there will be even more to come. Please join #draupnir:matrix.org if something breaks. You can find docker images here. If you are using Mjolnir, there are no migration steps, just change the image being used. You will also want to add draupnir to your additionalPrefixes in your config (or remove the additionalPrefixes entry entirely).

Changes of behaviour:

• The bot is now called draupnir, the code base still contains references to Mjolnir, but most of the documentation has been made consistent.

• An entirely new framework has been developed for parsing commands. Currently the commands that have changed are:
  - The ban command has changed to accept !draupnir ban <entity> [list] [reason]. You will now be prompted for missing arguments such as the list, which is useful when using a phone. Default reasons to be prompted with can be configured with commands.ban.defaultReasons.
  - The unban command has been changed to accept !draupnir unban [--true] <entity> [list]. Again, you will be prompted for the list to use. --true is only required if the entity that was unbanned is a glob.
  - The !mjolnir make admin command has been renamed !draupnir hijack room to stop people confusing it with the powerlevel command.
  - Errors experienced in commands using the new framework will be displayed to the management room with a uuid so that they can be easily discovered in the logs.

• watched policy lists are stored as matrix.to urls to room ids, any aliases will be resolved and stored as a room id. This is a different approach to what Mjolnir has taken where failing to resolve an alias to a watched list will silently fail. See Mjolnir#404

• The matrix-bot-sdk MatrixHttpClient & MatrixClientLite modules are now silenced. This was causing a lot of alarm fatigue and red herrings when debugging logs sent to us for Mjolnir, as any http error in the bot-sdk is logged at the error level. It can be re-enabled by changing the setting logMutedModules.

• JSX Templates can now be used to render the responses of commands. These can be transparently split across multiple messages if they render a message that is too large (currently this is clunky but the idea is later they will go into the same thread).

• Messages that are over the size limit will be split into a thread.

• !mjolnir status joins has been moved to !draupnir joins

Other things:

• !draupnir status now includes version information.
• New and old commands are shown in help, the information is still under development and is bare, but it still tells you about the arguments.
• Incorperate Mjolnir's new Policy List Manager by @Yoric in #5
• Incorperate: fix 2 issues in !config get by @jesopo in #15
• Rename the bot from Mjolnir to Draupnir in the documentation by @Gnuxie in #16

Full Changelog: v1.6.1...v1.80.0