Skip to content

Releases: serenity-rs/serenity

v0.9.1

08 Nov 17:00
d1dbf71
Compare
Choose a tag to compare

Thanks to the following for their contributions:

Changed

  • [gateway] Use the info level when notifying the user that a shard is running (@acdenisSK) c:7ea8098
  • [command_attr] Allow missing documentation for generated statics and functions (@acdenisSK) c:182ee78
  • [model] Change the use of the #[doc] attribute on VerificationLevel to doc comments (@nickelc) c:58e3d49
  • [misc] Reduce size of the crate by only including files that are necessary (@nickelc) c:a836180

Fixed

v0.9.0

30 Oct 22:52
8df4439
Compare
Choose a tag to compare

Thanks to the following for their contributions:

Added

Changed

v0.9.0-rc.4

24 Oct 19:22
b210a60
Compare
Choose a tag to compare

Thanks to the following for their contributions:

Changed

v0.9.0-rc.3

23 Oct 21:12
4dcbab7
Compare
Choose a tag to compare

Thanks to the following for their contributions:

Added

Changed

Fixed

Removed

v0.9.0-rc.2

27 Sep 20:43
7396f4e
Compare
Choose a tag to compare

Thanks to the following for their contributions:

Added

Changed

Fixed

Removed

  • [framework] Do not emit dispatch errors when ignoring bots or webhooks (@acdenisSK) c:41698b6

v0.9.0-rc.1

03 Sep 18:23
Compare
Choose a tag to compare

Thanks to the following for their contributions:

Added

Changed

Removed

v0.9.0-rc.0

11 Aug 14:21
Compare
Choose a tag to compare

Asynchronous Serenity

It has long been .awaited for, but it's finally here! Serenity now leverages async functions, thanks to the tokio runtime.

A big thanks goes to @Lakelezz. Without the dedication to her efforts, it wouldn't have been possible to make the switch easily.

Release candidate

As that is a huge change, among other changes, this is actually a testing release. It is encouraged to consumers of this release to provide feedback for any warts you might encounter, be it missing features, or bugs. One important bug is the OOM bug. After a period of time has passed since the bot connected, there might be a big random spike in memory usage, prompting the OOM killer to shutdown the bot's process. It is unknown where the spike comes from, or when exactly does it occur. It doesn't happen to every bot either. If you find your bot suddenly using a lot of memory, or being killed, please let us know by opening an Issue.

Thanks to the following for their contributions:

Added

Changed

Fixed

Removed

v0.8.7

11 Aug 12:53
Compare
Choose a tag to compare

This is a small release to publish a bunch of fixes the current branch has accumulated.

Thanks to the following for their contributions:

Changed

Fixed

  • [model] Fix User::nick_in unconditionally returning if the cache is passed (@acdenisSK) c:9c198ed
  • [CI] Fix the Linux CI job by adding the missing system dependency (@tweirtx) c:550a63c
  • [misc] Address some clippy warnings (@dmarcoux) c:2a54410
  • [utils] Preserve hostname when escaping invite links (@fenhl) c:7dd01eb
  • [voice] Fix .mute(...) not preventing the bot from sending frames. (@FelixMcFelix) c:638780e
  • [nidek] Fix doc-link to the Message::guild_id field in the Message::guild method (@SOF3) c:84b04ba
  • [framework] Fix check behaviour in the help command (@jmgao) c:e000833
  • [model] Fix the documentation order of permissions_for_role and permissions_for_user (@7596ff) c:9356a5c

v0.8.6

26 Apr 12:37
Compare
Choose a tag to compare

This release prevents a loop when requesting a restart of a Shard, resulting in the Shard hanging forever.

Thanks to the following for their contributions:

Fixed

v0.7.8

26 Apr 12:29
Compare
Choose a tag to compare

This release prevents a loop when requesting a restart of a Shard, resulting in the Shard hanging forever.

Thanks to the following for their contributions:

Fixed