New
v0.12.2
Thanks to the following for their contributions:
Unclaimed project
Are you a maintainer of serenity? Claim this project to take control of your public changelog and roadmap.
Thanks to the following for their contributions:
Continuing with the deprecations started in 0.12.1, many more methods and fields have been deprecated in order to make an easier upgrade path to 0.13.
These deprecation messages include a migration path, it is recommended to go one by one using cargo check and migrate each warning to reduce the burden migrating to 0.13. Following is a list of the deprecation PRs and the justification for these changes.
Channel::is_nsfw method was wrong, useless, and served better by GuildChannel::nsfwMember::highest_role_info is now strictly less powerful than the new Guild::member_highest_role and can avoid a cache lookup if used correctly.Guild::is_large is less accurate than Guild::largeMessage::is_own is super simple to implement yourselfMessage::is_private simply checks if Message::guild_id is none.Event::PresencesReplace does not exist, and is a relic from when serenity supported user accounts.TeamMember::permissions is always ["*"], so is useless.CreateMessage::enforce_nonce, to prevent sending duplicate messages.EditProfile::banner, allowing banners to be set for bots.ChannelId::get_thread_member.Guild::partial_member_permissions_in, which can be used to avoid fetching a Member in message events just to check permissions.From<User> for CreateEmbedAuthor, setting the author name and icon to the User's info.UserId::direct_message, so you don't need a full User to direct message.Http::default_allowed_mentions to set the AllowedMentions to be used with every request.Guild(Id)::bulk_ban, allowing bulk banning without hitting rate limits.