-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
fix(Message): update pinnable to check for migrated guilds
#11189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
This comment was marked as outdated.
This comment was marked as outdated.
59f3ace to
03bb75e
Compare
03bb75e to
01cf8f0
Compare
01cf8f0 to
b424b6f
Compare
advaith1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The migration has nothing to do with which permissions are usable - if you have either Manage Messages or Pin Messages you can pin. (as long as you also have read message history)
|
on that date manage messages will stop allowing pinning. that is separate from the guild feature |
Jiralite
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From internal discussions,1 we're going to require both permissions and make a release after removing MANAGE_MESSAGES.
Footnotes
Qjuh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from vlad's comment LGTM

Please describe the changes this PR makes and why it should be merged:
Resolves #11188