Skip to content

chore(deps): Update dependency net.dv8tion:JDA to v5.6.1 #71

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): Update dependency net.dv8tion:JDA to v5.6.1 #71

wants to merge 1 commit into from
+1 −1

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 7, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
net.dv8tion:JDA 5.0.0-beta.24 -> 5.6.1 age confidence

Release Notes

discord-jda/JDA (net.dv8tion:JDA)

v5.6.1

Bug Fixes

Full Changelog: discord-jda/JDA@v5.6.0...v5.6.1

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.6.1")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.6.1</version> 
</dependency>

v5.6.0: | ApplicationManager and minor improvements

Overview

This release introduces the ApplicationManager, which can be used to update the application's description and other settings through JDA.

New Features
Changes
Bug Fixes

Full Changelog: discord-jda/JDA@v5.5.1...v5.6.0

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.6.0")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.6.0</version> 
</dependency>

v5.5.1: | Bug fixes and performance improvements

Overview

This is a small release, including a bug fix for editCommand and editCommandById, as well as some performance improvements for looking up members by roles.

Additionally, you can now create threads with a custom slowmode.

New Features
Bug Fixes

Full Changelog: discord-jda/JDA@v5.5.0...v5.5.1

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.5.1")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.5.1</version> 
</dependency>

v5.5.0: | Improved voice state cache and file proxies

Changes to voice state cache (#​2835)

Voice states are now cached independently of guild members. JDA can now detect when a member connects or disconnects from an audio channel, even when the member is not currently cached.

With this change, you can technically use MemberCachePolicy.NONE and will still receive voice join / leave events, as long as CacheFlag.VOICE_STATE is enabled.

To reduce the memory footprint, we now only cache voice states if the member is connected to an audio channel. While disconnected, we will not keep the voice state cached, meaning we lose track of muted/deafend state and return an "empty" voice state for Member#getVoiceState.

Improvements to FileProxy (#​2782 and #​2727)

The FileProxy, ImageProxy, and AttachmentProxy now all support downloadAsFileUpload to easily stream a Discord proxies URL to a message.

@&#8203;Override
public void onMessageReceived(MessageReceivedEvent event) {
    List<Message.Attachment> attachments = event.getMessage().getAttachments();

    List<FileUpload> uploads = attachments.stream()
        .map(attachment ->
            attachment
                .getProxy()
                .downloadAsFileUpload(attachment.getWidth(), attachment.getHeight()))
        .collect(Collectors.toList());
    
    event.getChannel().sendFiles(uploads).queue();
}
New Features
Changes
Bug Fixes

Full Changelog: discord-jda/JDA@v5.4.0...v5.5.0

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.5.0")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.5.0</version> 
</dependency>

v5.4.0: | Interaction callback response and security incidents

Access the created or updated message from interaction replies (#​2798)

You can now use InteractionHook#getCallbackResponse to access the messages created by interaction replies.

@&#8203;Override
public void onSlashCommandInteraction(SlashCommandInteractionEvent event) {
  event.reply("React with your favorite emoji")
    .map(hook -> hook.getCallbackResponse().getMessage())
    .flatMap(message -> message.addReaction(emoji))
    .queue();
}

Previously, this could be done using an additional retrieveOriginal request. To reduce requests and improve responsiveness, we recommend preferring this new getter instead.

Guild security incidents (#​2577)

With guild security incidents, you can now be aware when Discord detects raids or spam in direct messages in a guild. These detections are available with Guild#getSecurityIncidentDetections and are updated with GuildUpdateSecurityIncidentDetectionsEvent.

Additionally, you can modify the security incident actions to temporarily pause invites or disable direct messages in your guild. See Guild#modifySecurityIncidents for details.

guild.modifySecurityIncidents(SecurityIncidentActions.enabled(
        // Pause invites for 2 hours
        OffsetDateTime.now().plusHours(2),
        // Disable direct messages for 1 hour
        OffsetDateTime.now().plusHours(1)
)).queue();

// Or disable security incident actions prematurely
guild.modifySecurityIncidents(SecurityIncidentActions.disabled()).queue();
New Features
Changes
Bug Fixes

Full Changelog: discord-jda/JDA@v5.3.2...v5.4.0

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.4.0")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.4.0</version> 
</dependency>

v5.3.2: | Bug fix for PrivateChannel#getName

Overview

Small bug fix release.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.3.1...v5.3.2

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.3.2")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.3.2</version> 
</dependency>

v5.3.1: | Bug fixes

Overview

Small bug fix release due to API changes regarding user-installed applications.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.3.0...v5.3.1

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.3.1")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.3.1</version> 
</dependency>

v5.3.0: | User-Installable Apps

Overview

After many months of waiting, this release finally adds support for user-installable apps. This will allow you to make use of interactions (and especially commands) anywhere on Discord, by installing the application on a user directly instead of a guild.

Creating User-Installable Apps

To create a user-installable app, you first have to enable the feature in your application dashboard in the installation settings:

firefox_X9eJoKZ88K

Once enabled, you can create user-installable commands, by changing the integration types:

Commands.slash("say", "Makes the bot say what you tell it to")
// Allow the command to be used anywhere (Bot DMs, Guild, Friend DMs, Group DMs)
  .setContexts(InteractionContextType.ALL) 
// Allow the command to be installed on users instead of guilds
  .setIntegrationTypes(IntegrationType.USER_INSTALL) 
  .addOption(STRING, "content", "What the bot should say", true)
Installing to a User

To actually install your app to a user, you can use the generator provided by discord. In the OAuth2 URL Generator, change the integration type to User Install:

firefox_VGe9NK4Xld

The generated link, can now be used to install your application to the authorizing user.

image

Detached Guilds / Roles / Channels / Members

This comes with a few changes to expectations around JDA functionality. Since interactions can now come from anywhere on Discord, some features aren't available in certain contexts.

Some entities can now appear as Detachable Entity, which essentially means that they come from a guild or private channel, that your bot is not directly involved in.

For instance, if a command is installed on a user and that command is used in a guild, your bot is not necessarily a member of that guild. Since the bot is not a member, it only has access to the guild context, that the interaction event provides. Many features such as channels, roles, or members are not accessible without being an actual member of the guild. If you try to use or access anything that isn't accessible, JDA will throw a new DetachedEntityException.

New Features

Full Changelog: discord-jda/JDA@v5.2.3...v5.3.0

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.3.0")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.3.0</version> 
</dependency>

v5.2.3

Small bug fix release.

Bug Fixes
Changes

Full Changelog: discord-jda/JDA@v5.2.2...v5.2.3

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.2.3")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.2.3</version> 
</dependency>

v5.2.2

Small bug fix release.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.2.1...v5.2.2

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.2.2")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.2.2</version> 
</dependency>

v5.2.1

Small bug fix release.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.2.0...v5.2.1

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.2.1")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.2.1</version> 
</dependency>

v5.2.0: | Application emoji and premium buttons

Overview

This release adds some new features for applications. We've also started working on more compliance tests to make contributing and reviewing changes easier.

Premium Buttons (#​2752)

The interaction response replyWithPremiumRequired is being phased out in favor of custom messages with a new button style Button.premium(sku) to upsell specific premium features instead.

You can change your code to a simple reply(content) with this button as a component.

event.reply("This feature is only available for premium users.")
  .addActionRow(Button.primary(SkuSnowflake.fromId(PREMIUM_FEATURE_SKU)))
  .setEphemeral(true)
  .queue();

For more info, see the official Discord Changelog.

Application Emoji (#​2726)

Your bot can now manage emoji with JDA by using JDA#createApplicationEmoji. These emojis can then be used like any other emoji with Emoji.fromCustom(name, id, animated).

New Features
Bug Fixes
Changes

Full Changelog: discord-jda/JDA@v5.1.2...v5.2.0

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.2.0")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.2.0</version> 
</dependency>

v5.1.2: | Message Forwarding and Voice Messages

Overview

This release adds support for new message features.

Forwarding messages (#​2744)

You can now handle forwarded messages using the new message snapshots.

@&#8203;Override
public void onMessageReceived(MessageReceivedEvent event) {
    MessageReference messageReference = event.getMessage().getMessageReference();
    // Forwarded messages have a reference of type FORWARD
    if (messageReference != null && messageReference.getType() == MessageReference.MessageReferenceType.FORWARD) {
        // The content of the forwarded message is provided as a snapshot
        MessageSnapshot snapshot = event.getMessage().getMessageSnapshots().getFirst();
        System.out.println("Received forwarded message with content: " + snapshot.getContentRaw());
    }
}

A bot can also forward a message using Message#fowardTo. Note that a forwarded message cannot contain any additional content.

Voice messages (#​2738)

You can now send voice messages with JDA, by utilizing the new FileUpload#asVoiceMessage method on your audio attachments.

channel.sendFiles(
  FileUpload.fromData(audioFile)
    .asVoiceMessage(MediaType.parse("audio/ogg"), waveform, 10.5) // 10.5 seconds audio/ogg message
).queue();

To create a voice message, you must first determine the audio media type of your voice message and sample a waveform up to 256 bytes. Voice messages require a valid audio/* media type like audio/ogg.

The waveform is used to render the voice message shape in the preview. It must not be an accurate sampling of the actual audio.

New Features

Bug Fixes

Full Changelog: discord-jda/JDA@v5.1.1...v5.1.2

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.1.2")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.1.2</version> 
</dependency>

v5.1.1: | Small bugfix release

Overview

Small release to fix a few bugs. This fixes an issue that caused voice receive to no longer work as intended in 5.1.0.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.1.0...v5.1.1

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.1.1")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.1.1</version> 
</dependency>

v5.1.0: | Voice Gateway v8

Overview

This release updates the implementation of the voice gateway to API version 8 (previously 4). Previous versions will be incompatible coming November 18, 2024. This includes adding a new dependency on tink, to support the new encryption modes.

Additionally, the MessageEmbedEvent has been removed. Discord sends standard update events for embed loading now, this event can no longer be supported.

New Features
Changes
Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.2...v5.1.0

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.1.0")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.1.0</version> 
</dependency>

v5.0.2: | Single time event listener

Overview

This release includes some bug fixes as well as a new event listener feature to add a one-time-use event listener.

Once Event Listener (#​2683)

A common problem that developers run into, is "waiting" for a specific event in the context of some command. For instance, waiting for a user to add a reaction or reply with a message in response to some prompt.

This can now be achieved using the new listenOnce event listener:

// listen for a message event
jda.listenOnce(MessageReceivedEvent.class)
    // filter for specific event
    .filter(event -> event.getChannel().equals(channel))
    .filter(event -> event.getAuthor().equals(user))
    // handle timeout
    .timeout(timeout, () -> hook.editOriginal("Timeout!").queue())
    // subscribe to first event that matches filters
    .subscribe(event -> {
        hook.editOriginal("You sent: " + event.getMessage().getContentRaw()).queue();
    });

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.1...v5.0.2

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.2")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.2</version> 
</dependency>

v5.0.1: | Hotfix shard manager thread handling

Overview

Small hotfix release, fixes problem with default thread config for DefaultShardManager. This caused requests to fail if a shard is stopped or restarted.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0...v5.0.1

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.1")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.1</version> 
</dependency>

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:

As well as more specific features or attributes of channels:

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();
if (channel.getType() == TEXT) {
  channel.asTextChannel().getManager().setTopic("test topic").queue();
}

Cache access has also seen some improvement, by introducing a new getChannelById(Class, long) method, allowing to just get a MessageChannel without worrying about the concrete type.

GuildMessageChannel channel = guild.getChannelById(GuildMessageChannel.class, 125227483518861312L);
channel.sendMessage("Hello general chat!").queue();

Learn more about the channel rework in Channel Rework.

Message Features

We've refactored our message sending interfaces to be more consistent, by abstracting MessageAction, MessageBuilder, and ReplyAction into shared interfaces MessageCreateRequest and MessageEditRequest. This makes all message sending code consistent. We recommend to simply chain your builder-like code directly on send messages:

channel.sendMessage("Hello World")
  .setComponents(ActionRow.of(button1, button2))
  .setEmbeds(embed1, embed2)
  .setFiles(files)
  .queue();

However, if you need to use builders, we've introduced MessageEditBuilder and MessageCreateBuilder to replace the old MessageBuilder utility. You can also now use SplitUtil to easily divide message content into multiple messages.

To support file descriptions and reduce the number of sendFile overloads, we've also introduced a new FileUpload type that unifies all attachments into a single type.

FileUpload file = FileUpload.fromData(new File("myFile.png"), "image.png")
  .setDescription("this is my alt text for screenreaders, allowing to make accessible images in your messages!");
channel.sendFiles(file).queue();

Learn more about the changes to message sending in Message Send/Edit Rework.

Emojis and Stickers

In JDA 5, we have decided to unify all emoji types into a consistent type structure:

These new emoji types replace the duplication of ReactionEmote and Activity.Emoji.

Stickers have also been refactored in a similar way, making a clear distinction between stickers found in messages and guild settings:

  • Sticker, a top-level abstraction of all sticker types
  • StickerItem, stickers found in messages
  • RichSticker, stickers with more information that is usually omitted for messages (sticker items)
  • StandardSticker, rich stickers provided by nitro instead of guilds
  • GuildSticker, rich stickers provided in guilds
  • StickerUnion, adding type casting

Learn more about the changes to emojis and stickers in Sticker and Emoji Rework.

Installation

All future JDA releases will be distributed through maven central. You no longer need to use jcenter() in your dependency manager.

Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0</version> 
</dependency>
Changelog (5.0.0-beta.24 -> 5.0.0)

The changes since the latest beta release to this release.

Changelog (4.4.0 -> 5.0.0)

Note that this changelog is a linear history of changes. This means some earlier changes have already been superseded or refined in more recent changes. This changelog is slightly compressed to remove unimportant changes, you can see the full list of commits here.

Thank you all for contributing!

New Features
New feature additions since 4.4.0

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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Jul 7, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Jul 7, 2024 •
edited
Loading

Test Results

9 tests  ±0   9 ✅ ±0   0s ⏱️ ±0s
3 suites ±0   0 💤 ±0 
3 files   ±0   0 ❌ ±0 

Results for commit 613442f. ± Comparison against base commit 168ac80.

This pull request removes 4 and adds 4 tests. Note that renamed tests count towards both. 
org.incendo.cloud.discord.slash.StandardOptionRegistryTest ‑ [1] clazz=class java.lang.String, expected=DiscordOptionType{name=STRING, value=3, type=io.leangen.geantyref.TypeToken$1@6aaf03a}
org.incendo.cloud.discord.slash.StandardOptionRegistryTest ‑ [2] clazz=class java.lang.Integer, expected=DiscordOptionType{name=INTEGER, value=4, type=io.leangen.geantyref.TypeToken$1@2d645ed1}
org.incendo.cloud.discord.slash.StandardOptionRegistryTest ‑ [3] clazz=class java.lang.Boolean, expected=DiscordOptionType{name=BOOLEAN, value=5, type=io.leangen.geantyref.TypeToken$1@69c9a597}
org.incendo.cloud.discord.slash.StandardOptionRegistryTest ‑ [4] clazz=class java.lang.Double, expected=DiscordOptionType{name=NUMBER, value=10, type=io.leangen.geantyref.TypeToken$1@30386049}

org.incendo.cloud.discord.slash.StandardOptionRegistryTest ‑ [1] clazz=class java.lang.String, expected=DiscordOptionType{name=STRING, value=3, type=io.leangen.geantyref.TypeToken$1@4b1210ee}
org.incendo.cloud.discord.slash.StandardOptionRegistryTest ‑ [2] clazz=class java.lang.Integer, expected=DiscordOptionType{name=INTEGER, value=4, type=io.leangen.geantyref.TypeToken$1@5bc79255}
org.incendo.cloud.discord.slash.StandardOptionRegistryTest ‑ [3] clazz=class java.lang.Boolean, expected=DiscordOptionType{name=BOOLEAN, value=5, type=io.leangen.geantyref.TypeToken$1@e350b40}
org.incendo.cloud.discord.slash.StandardOptionRegistryTest ‑ [4] clazz=class java.lang.Double, expected=DiscordOptionType{name=NUMBER, value=10, type=io.leangen.geantyref.TypeToken$1@1acaf3d}

♻️ This comment has been updated with latest results.

@renovate renovate bot force-pushed the renovate/jda5 branch from 14a3c0f to 439f8e0 Compare July 15, 2024 18:14
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.0.0 chore(deps): Update dependency net.dv8tion:JDA to v5.0.1 Jul 15, 2024
@renovate renovate bot force-pushed the renovate/jda5 branch from 439f8e0 to 39a4627 Compare August 4, 2024 15:06
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.0.1 chore(deps): Update dependency net.dv8tion:JDA to v5.0.2 Aug 4, 2024
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.0.2 chore(deps): Update dependency net.dv8tion:JDA to v5.1.0 Aug 21, 2024
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.1.0 chore(deps): Update dependency net.dv8tion:JDA to v5.1.1 Sep 21, 2024
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.1.1 chore(deps): Update dependency net.dv8tion:JDA to v5.1.2 Oct 5, 2024
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.1.2 chore(deps): Update dependency net.dv8tion:JDA to v5.2.0 Nov 3, 2024
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.2.0 chore(deps): Update dependency net.dv8tion:JDA to v5.2.1 Nov 10, 2024
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.2.1 chore(deps): Update dependency net.dv8tion:JDA to v5.2.2 Dec 27, 2024
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.2.2 chore(deps): Update dependency net.dv8tion:JDA to v5.2.3 Jan 26, 2025
@renovate renovate bot force-pushed the renovate/jda5 branch 2 times, most recently from b2f00b5 to cb54f9f Compare February 2, 2025 17:03
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.2.3 chore(deps): Update dependency net.dv8tion:JDA to v5.3.0 Feb 2, 2025
@renovate renovate bot force-pushed the renovate/jda5 branch from cb54f9f to 0126dc8 Compare March 27, 2025 19:01
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.3.0 chore(deps): Update dependency net.dv8tion:JDA to v5.3.1 Mar 27, 2025
@renovate renovate bot force-pushed the renovate/jda5 branch from 0126dc8 to 84bc0ac Compare April 5, 2025 10:29
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.3.1 chore(deps): Update dependency net.dv8tion:JDA to v5.3.2 Apr 5, 2025
@renovate renovate bot force-pushed the renovate/jda5 branch from 84bc0ac to 2c230f1 Compare April 20, 2025 19:10
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.3.2 chore(deps): Update dependency net.dv8tion:JDA to v5.4.0 Apr 20, 2025
@renovate renovate bot force-pushed the renovate/jda5 branch from 2c230f1 to 591f504 Compare April 27, 2025 19:21
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.4.0 chore(deps): Update dependency net.dv8tion:JDA to v5.5.0 Apr 27, 2025
@renovate renovate bot force-pushed the renovate/jda5 branch from 591f504 to 1ec6637 Compare May 3, 2025 13:52
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.5.0 chore(deps): Update dependency net.dv8tion:JDA to v5.5.1 May 3, 2025
@renovate renovate bot force-pushed the renovate/jda5 branch from 1ec6637 to daf6579 Compare June 7, 2025 22:36
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.5.1 chore(deps): Update dependency net.dv8tion:JDA to v5.6.0 Jun 7, 2025
@renovate renovate bot force-pushed the renovate/jda5 branch from daf6579 to 613442f Compare June 8, 2025 22:11
@renovate renovate bot changed the title chore(deps): Update dependency net.dv8tion:JDA to v5.6.0 chore(deps): Update dependency net.dv8tion:JDA to v5.6.1 Jun 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants