v0.4.3

Allows the server to start. Oops.

v0.4.2

Further fixes to the docker build. More oops.

v0.4.1-2

Fixes the Docker build (oops).

v0.4.1

What's Changed

• Address problematic confusable (%) by @Archasion in #37
• Replace mentions in message content with corresponding usernames by @Archasion in #38
• Implement native moderation as actions: ban, kick, and timeout by @Archasion in #39
• Rust version is now 1.73.0
• Sentry tweaked; should report less issues for flaky errors and also be initialized correctly in async environments

New Contributors

• @Archasion made their first contribution in #37

Full Changelog: v0.4.0...v0.4.1

v0.4.0

Three changes of note in this release:

• Dependencies updated, most importantly including an update to Twilight 0.14.x, which should fix some issues with unknown Discord events generating really spammy error output.
• #33 resolved: the filter that failed is now included in the /chrysanthemum-test output.
• Command handling redone yet again. Should be more robust in general, and will also clean up old commands if and when the time comes to move one around.

v0.3.0

This is a breaking change. The slash command configuration has changed. Previously, you could specify a set of roles and users that would have access to each slash command. This is no longer the case; Discord does not allow this endpoint to be accessed by bot tokens anymore. Slash commands can now only be enabled/disabled on a per-guild basis.

v0.2.19

Updated dependencies. We now build the Docker image based on Rust 1.61.0.

v0.2.18

• Updated to Twilight 0.11.x.
• Stopped logging non-panic errors to Sentry.
• Added MESSAGE_CONTENT intent to ensure Chrysanthemum receives message contents.
• Minor code cleanup (clippy).

v0.2.17

Fixes release builds (oops).

v0.2.16

What's Changed

• Report more stuff to Sentry #32
• Filtered messages with empty content crash Chrysanthemum (#29) is resolved
• Wrap filtered message content in a code block (#30) is resolved

Full Changelog: v0.2.15...v0.2.16