fix(deps): update rust crate serenity to v0.12.2 #264
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mchesterbot[bot]](https://avatars.githubusercontent.com/in/202745?s=60&v=4){kind=small}
| datasource | package | from | to | | ---------- | -------- | ------ | ------ | | crate | serenity | 0.12.1 | 0.12.2 |
mchesterbot
bot
force-pushed
the
renovate/serenity-0.x-lockfile
branch
from
bbf78ee
to
a205354
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.12.1->0.12.2Release Notes
serenity-rs/serenity (serenity)
v0.12.2Compare Source
Thanks to the following for their contributions:
Deprecations
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 checkand 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_nsfwmethod was wrong, useless, and served better byGuildChannel::nsfwMember::highest_role_infois now strictly less powerful than the newGuild::member_highest_roleand can avoid a cache lookup if used correctly.Guild::is_largeis less accurate thanGuild::largeMessage::is_ownis super simple to implement yourselfMessage::is_privatesimply checks ifMessage::guild_idisnone.Event::PresencesReplacedoes not exist, and is a relic from when serenity supported user accounts.TeamMember::permissionsis always["*"], so is useless.Other notable changes
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 aMemberin message events just to check permissions.From<User>forCreateEmbedAuthor, setting the author name and icon to theUser's info.UserId::direct_message, so you don't need a fullUserto direct message.Http::default_allowed_mentionsto set theAllowedMentionsto be used with every request.Guild(Id)::bulk_ban, allowing bulk banning without hitting rate limits.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.