Skip to content
This repository has been archived by the owner on May 19, 2024. It is now read-only.

Update dependency net.dv8tion:JDA to v5.0.0-beta.24 #40

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency net.dv8tion:JDA to v5.0.0-beta.24 #40

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 29, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
net.dv8tion:JDA 5.0.0-beta.13 -> 5.0.0-beta.24 age adoption passing confidence

Release Notes

DV8FromTheWorld/JDA (net.dv8tion:JDA)

v5.0.0-beta.24: | Bug fixes and entitlement types

Compare Source

Overview

This is a small bugfix release, including some missing features for premium app entitlements.

Additional Entitlement Features (#​2667)

This release adds support for test entitlements and consumed entitlements.

An entitlement can be consumed, marking it as already used. This can be useful for one-time entitlements, which are consumed on use.

public boolean hasEntitlement(long skuId, List<Entitlement> entitlements) {
  return entitlements.stream().anyMatch(e -> e.getSkuIdLong() == skuId && !e.isConsumed());
}
public void consumeEntitlement(long skuId, List<Entitlement> entitlements) {
  entitlements.stream()
    .filter(e -> e.getSkuIdLong() == skuId && !e.isConsumed())
    .findFirst()
    .ifPresent(entitlement -> entitlement.consume().queue());
}

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.23...v5.0.0-beta.24

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.24")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.24</version> 
</dependency>

v5.0.0-beta.23: | Message Polls

Compare Source

Overview

This release includes an updated README, please let us know if you spot any issues with it!

Polls (#​2649)

Discord has recently released a new feature on their platform to start and vote in polls. These polls can now be sent in messages:

channel.sendMessage("Hello guys! Check my poll:")
  .setPoll(
    MessagePollData.builder("Which programming language is better?")
      .addAnswer("Java", Emoji.fromFormatted("<:java:1006323566314274856>"))
      .addAnswer("Kotlin", Emoji.fromFormatted("<:kotlin:295940257797636096>"))
      .build())
  .queue()

The poll automatically expires after a set duration, configurable in the MessagePollBuilder using setDuration. A poll can also be ended manually using endPoll or endPollById.

You can check the poll votes on a message using the new Message#getPoll:

MessagePoll poll = message.getPoll();
for (MessagePoll.Answer answer : poll.getAnswers()) {
  System.out.printf("Poll Answer %s has %d votes\n", answer.getText(), answer.getVotes());
}

[!NOTE]
The votes for polls are eventually consistent and need to be recounted after the poll ends. You can check whether the votes are validated using MessagePoll#isFinalizedVotes.

New Features

Changes

Bugs Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.22...v5.0.0-beta.23

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.23")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.23</version> 
</dependency>

v5.0.0-beta.22: | Bulk ban, premium apps, bug fixes

Compare Source

Overview

This release adds some newer API features, like premium app subscriptions, bot banners, and bulk banning users.

Besides new features, this release also includes improved errors and bug fixes.

Premium App Subscriptions (#​2583)

If your bot is eligible for monetization, you can now use JDA to handle entitlements in interactions to restrict features. With event.replyWithPremiumRequired(), you can upsell a premium subscription to a user:

b306d1ccc7205d2291f4535f912a790e

Read more about entitlements and premium app subscriptions in the Discord Developer Docs.

Bulk Ban (#​2630)

You can now ban up to 200 users in one request using guild.ban(users, messageDeleteTimeframe).

This endpoint has a few quirks to keep in mind:

  • The BulkBanResponse includes failed users and banned users
  • If a user was already banned, they are in the failed users
  • If you don't have permissions to ban a user (higher role / owner), they also appear in failed users
  • The self user also appears in failed users
  • If all users "failed" you get an error response instead

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.21...v5.0.0-beta.22

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.22")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.22</version> 
</dependency>

v5.0.0-beta.21: | Bug fixes and enforced nonce on messages

Compare Source

Overview

This release fixes a few bugs but also implements a new behavior on message sending.

With the new enforce nonce behavior, messages will no longer be duplicated due to timeouts or discord outages. This means, any message request will now send an automatically generated nonce. You can still set a custom nonce using setNonce, but you should make sure that this nonce is unique. If you previously relied on this setter, ensure that you are not sending duplicated nonce values.

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.20...v5.0.0-beta.21

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.21")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.21</version> 
</dependency>

v5.0.0-beta.20: | Bug fixes and internal refactoring

Overview

With this release, we reworked a lot of internals related to how we cache channels. Ideally, you should not notice any difference.

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.19...v5.0.0-beta.20

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.20")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.20</version> 
</dependency>

v5.0.0-beta.19: | Bug fixes and voice channel status

Overview

Smaller release with some bug fixes and added support for voice channel status feature.

Voice Channel Status (#​2532)

Bots can now configure the voice channel status, shown when opening a voice channel in full screen mode. This works similarly to a channel topic, but can be configured by everyone who is currently connected to the channel.

The new VOICE_SET_STATUS permission indicates whether a user can change the channel status while they are connected. When a user is not connected to the channel, the MANAGE_CHANNEL permission is required instead (similar to topics).

Note that this feature might be replaced by a new "hang status" in the future, which would instead show on the user rather than the channel.

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.18...v5.0.0-beta.19

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.19")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.19</version> 
</dependency>

v5.0.0-beta.18

Compare Source

Overview

This release fixes a race-condition in the default rate-limiter implementation that very rarely resulted in an orphaned rate-limit bucket.

Orphan Rate-Limit Buckets (#​2585)

Sometimes the cleanup of buckets resulted in an active rate-limit bucket being orphaned. This means that the bucket was continuously trying to execute the same request without updating its state.

This release should resolve that problem, fixing the occasional bug where a 429 response was handled incorrectly.

New Thread Model (#​2463)

The default thread model used for the handling of rate-limits has been changed. Instead of using a single scheduled executor, we now make use of an additional elastic pool that automatically scales up and down based on how many buckets run concurrently.

In the previous model, the scheduled executor limited the capabilities by only providing a fixed amount of threads. To handle scaling with larger bots, we simply used 5 threads for each shard. This has been adjusted now to use a shared pool, which scales up and down based on load instead.

Please let us know if you run into any problems with the defaults in your deployments!

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.17...v5.0.0-beta.18

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.18")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.18</version> 
</dependency>

v5.0.0-beta.17: | Fix webhooks in thread channels

Compare Source

Overview

This release fixes some issues with webhook executions in thread channels.

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.16...v5.0.0-beta.17

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.17")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.17</version> 
</dependency>

v5.0.0-beta.16: | Webhook Execution and Super Reactions

Compare Source

Overview

With this release, we have redesigned a major flaw in our entity constraints. Previously, message instances required a known cached channel instance to be usable. This flaw has been remedied by reworking this implementation to be usable with only a known channel id.

This means, that methods such as message.addReaction(...) or message.pin() can now work for message instances that have no channel object in cache. You can find out if a channel is available on a message instance, by using hasChannel. Adding support for this behavior was necessary, in order to implement webhook executions!

With this change resolved, we can now fully support sending messages through arbitrary webhooks by using WebhookClient.createClient. This webhook client makes use of the JDA rate-limit system and request queue, to properly handle rate-limits for you.

Interactions Hidden Threads

This release also fixes the problem of not receiving interactions in hidden threads, for instance if the thread is a private thread and your bot has not been added yet. This problem was actually caused by JDA expecting a channel instance in cache that was not present, which stopped the interaction from going through.

Discord has added more information about the channel objects in interactions, so we can now properly construct the thread channel instance just in time for the interaction event.

Super Reactions

Your bot can now tell what super-reactions are used. You still cannot send them because the API is too unstable.

Beta Period Almost Done!

We plan to end the beta period for JDA 5.0.0 very soon. There are a few more changes we are thinking of merging first, but the current release already seems very complete. We hope to end the beta period before the end of the year, stay tuned.

New Features

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.15...v5.0.0-beta.16

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.16")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.16</version> 
</dependency>

v5.0.0-beta.15: | Bug fixes

Compare Source

Overview

This release fixes a bug introduced by 5.0.0-beta.14.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.14...v5.0.0-beta.15

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.15")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.15</version> 
</dependency>

v5.0.0-beta.14: | Media Channels, Custom Status, LRU Cache

Compare Source

Overview

This brings JDA up to date with newly released API features and fixes a few issues.

Support for Custom Status (#​2521)

Many years ago, the "Custom Status" feature has been released on Discord, but has since been limited to client users. With a change recently, bots have finally been granted access to set this custom status as well. This, however, is limited to only setting the text value and no emoji.

You can set a custom status using Activity.customStatus(text).

Media Channels (#​2516)

Discord is rolling out another new channel type. This time the type is a derivation of forum channels, specifically designed to share media such as images or videos. This release adds support for media channels.

A few places now return the new abstraction IPostContainer, where previously a ForumChannel was used. This abstraction is used to deduplicate and expand the API to handle both media and forum channels equally, as both of these types handle posts (threads with start messages).

LRU Member Cache (#​2506)

The member cache has become slightly more powerful by introducing the new LRUMemberCachePolicy. A Least-Recently-Used (LRU) cache keeps members cached based on activity.

Example:

MemberCachePolicy.VOICE                             // Keep in cache if currently in voice (skip LRU and ONLINE)
    .or(MemberCachePolicy.ONLINE)                   // Otherwise, only add to cache if online
    .and(MemberCachePolicy.lru(1000)                // keep 1000 recently active members
        .unloadUnless(MemberCachePolicy.VOICE))     // only unload if they are not in voice

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.13...v5.0.0-beta.14

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.14")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.14</version> 
</dependency>

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.14 Update dependency net.dv8tion:JDA to v5.0.0-beta.15 Sep 30, 2023
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.15 Update dependency net.dv8tion:JDA to v5.0.0-beta.16 Oct 22, 2023
@renovate renovate bot force-pushed the renovate/jda branch 2 times, most recently from 8d2a29a to c64d804 Compare October 29, 2023 15:10
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.16 Update dependency net.dv8tion:JDA to v5.0.0-beta.17 Oct 29, 2023
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.17 Update dependency net.dv8tion:JDA to v5.0.0-beta.18 Nov 19, 2023
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.18 Update dependency net.dv8tion:JDA to v5.0.0-beta.19 Jan 1, 2024
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.19 Update dependency net.dv8tion:JDA to v5.0.0-beta.20 Jan 21, 2024
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.20 Update dependency net.dv8tion:JDA to v5.0.0-beta.21 Mar 10, 2024
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.21 Update dependency net.dv8tion:JDA to v5.0.0-beta.22 Apr 6, 2024
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.22 Update dependency net.dv8tion:JDA to v5.0.0-beta.23 Apr 21, 2024
@renovate renovate bot force-pushed the renovate/jda branch from b4b570b to 8c7c990 Compare May 12, 2024 15:27
@renovate renovate bot changed the title Update dependency net.dv8tion:JDA to v5.0.0-beta.23 Update dependency net.dv8tion:JDA to v5.0.0-beta.24 May 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

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