fix(deps): update dependency net.dv8tion:jda to v6.1.3 [security] #767
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.0.0-rc.5→6.1.3Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
GHSA-93fv-4pm9-xp28
Impact
Anyone using untrusted message components may be affected. On versions >=6.0.0,<6.1.3 of JDA, the requester will attempt to download external media URLs from components if they are used in an update or send request.
If you are used
Message#getComponentsor similar to get a list of components and then send those components withsendMessageComponentsor other methods, you might unintentionally download media from an external URL in the resolved media of aThumbnail,FileDisplay, orMediaGallery.Patches
This bug has been fixed in 6.1.3, and we recommend updating.
Workarounds
Avoid sending components from untrusted messages or update to version 6.1.3.
Release Notes
discord-jda/JDA (net.dv8tion:JDA)
v6.1.3Bug Fixes
Full Changelog: discord-jda/JDA@v6.1.2...v6.1.3
Installation
Gradle
Maven
v6.1.2Bug Fixes
Full Changelog: discord-jda/JDA@v6.1.1...v6.1.2
Installation
Gradle
Maven
v6.1.1New Features
Bug Fixes
ModalMapping::getAsAttachmentListif no attachments were submitted by @archer-321 in #2941Full Changelog: discord-jda/JDA@v6.1.0...v6.1.1
Installation
Gradle
Maven
v6.1.0: | Modal File UploadsOverview
This release primarily adds support for file uploads in modals.
Creating a Modal accepting file uploads
Using the uploaded file
New Features
Invite.Guildfields by @freya022 in #2914Full Changelog: discord-jda/JDA@v6.0.0...v6.1.0
Installation
Gradle
Maven
v6.0.0: | New Component APICompare Source
Overview
This is the stable release of JDA 6.0.0. To avoid repeating the same information again, please look at the release notes of the release candidates for detailed explanations of the breaking changes and new features.
Release Candidates
Migrating to 6.0.0
To help ease the upgrade to JDA 6.0.0, we've provided an OpenRewrite recipe that can automatically refactor parts of your codebase. This will update imports and replace a few method calls with their new equivalents in JDA 6.0.0.
However, not all breaking changes can be handled automatically — for example, code that relied on the mutability of
ActionRowwill require manual adjustments.You will also have to update your code for creating
Modalinstances. Instead of usingActionRow, modals now make use of theLabelcomponent. Read the release notes for v6.0.0-rc.4 to learn more.The OpenRewrite Recipe
Before applying the recipe, make sure you’re using version control (e.g., Git) or back up your project manually. You’ll also need to be using Gradle or Maven to apply the migration.
Gradle
We are using the OpenRewrite Gradle Plugin. Before changing your JDA version in gradle, you can add the rewrite plugin and use the recipe to migrate your code:
Once you configured this plugin, you can use the
rewriteDryRuntask to generate a git patch inbuild/reports/rewrite/rewrite.patchto see what the plugin will do with your source code. To apply the changes, either use this patch or userewriteRun.After migrating your code, you can then update your JDA version (if the rewrite hasn't done it already) and remove the plugin again.
Maven
We are using the OpenRewrite Maven Plugin. Before changing your JDA version in your pom, you can add the rewrite plugin and use the recipe to migrate your code:
Once you configured this plugin, you can use the
rewrite:dryRuntask to generate a git patch intarget/site/rewrite/rewrite.patchto see what the plugin will do with your source code. To apply the changes, either use this patch or userewrite:run.After migrating your code, you can then update your JDA version (if the rewrite hasn't done it already) and remove the plugin again.
New Features
Changes
interactionspackage by @freya022 in #2890Bug Fixes
DELETE_GUILDroute according to the Discord Docs by @kiLeo13 in #2875Full Changelog: discord-jda/JDA@v5.6.1...v6.0.0
Installation
Gradle
Maven
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.