Bump net.dv8tion:JDA from 5.0.0-beta.24 to 5.0.0

[dependabot]

Bumps net.dv8tion:JDA from 5.0.0-beta.24 to 5.0.0.

Release notes

Sourced from net.dv8tion:JDA's releases.

v5.0.0 | End of beta phase

The Long Awaited Stabilization

After almost 3 years of refactoring and polishing, the stabilization of JDA 5.0.0 is here. If you have been following along, not much has changed since the latest beta release.

If you have somehow avoided updating to a beta release since 2021, here is a list of the most noteworthy additions, changes, and bug fixes since 4.4.0.

You can also use our Migration Guide to help you update to the latest version of JDA 5. This guide also includes the most important changes you need to consider.

Interactions / Application Features

Discord has further improved the capabilities of applications with new types of interactions. This major release of JDA adds support for these features, coming with some restructuring to properly accomodate the new types.

We've renamed interaction events to a more consistent naming scheme:

• SlashCommandEvent becomes SlashCommandInteractionEvent
• ButtonClickEvent becomes ButtonInteractionEvent

Similarly, we've renamed component types slightly:

• SelectionMenu is now StringSelectMenu, while adding a new EntitySelectMenu
• What was previously called Component has now been renamed to ActionComponent and ItemComponent, allowing us to introduce Component as an abstraction over both Button and ActionRow (which is now a LayoutComponent). The new Component interface is now an abstraction over both ItemComponent and LayoutComponent.

To learn more about interactions in JDA 5, take a look at our Interactions Wiki Guide.

Channel Type Rework

We've refactored the channel types and usages in JDA to be more maintainable. Each type of channel now directly maps to a specific channel interface, unlike before where VoiceChannel was used for both stage and voice type channels.
Instead there are now concrete interfaces for each type, such as NewsChannel, StageChannel, ForumChannel, etc.

The channel type hierarchy has been further refined, by introducing higher level abstractions to represent the features of multiple channel types:

• Channel
• GuildChannel
• MessageChannel and GuildMessageChannel
• AudioChannel

As well as more specific features or attributes of channels:

• IPermissionContainer
• IPositionableChannel
• IThreadContainer
• IWebhookContainer
• etc.

To properly maintain these many different channel types and make them easy to use, we've also introduced new union types to encompass multiple channels into a simple common union type. This replaces the old getTextChannel()/getVoiceChannel() getters on events with getChannel().asTextChannel(). However, you can also use the standard features of the unions directly. For instance, a MessageChannelUnion allows to send messages and these specialization methods:

MessageChannelUnion channel = event.getChannel();
channel.sendMessage("hello").queue();
</tr></table> 

... (truncated)

Commits

• 2269f42 Update nexus publishing plugin
• 526ed45 Bump to 5.0.0
• cf00f6c Update and remove deprecated symbols (#2686)
• f4b9092 Fix inconsistent bug template descriptions (#2697)
• 6ae83e3 Add missing permissions (#2690)
• 6d977de Update ErrorResponse enum (#2693)
• 9fc38fe Improve Unknown Interaction error responses (#2687)
• 890fdf2 Update MessageType enum (#2691)
• 6188f58 Add missing permissions in ALL_[TEXT/VOICE]_PERMISSIONS (#2692)
• 4616946 Allow UserSnowflake subtypes in bulk ban methods (#2689)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)