Skip to content
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

Update dependency net.dv8tion:JDA to v5.0.0-beta.16 #55

Merged
merged 1 commit into from
Oct 23, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 22, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

DV8FromTheWorld/JDA (net.dv8tion:JDA)

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>

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.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@DxsSucuk DxsSucuk merged commit 1825d45 into master Oct 23, 2023
6 checks passed
@DxsSucuk DxsSucuk deleted the renovate/net.dv8tion-jda-5.x branch October 23, 2023 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant