This repository has been archived by the owner on Feb 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Update dependency net.dv8tion:JDA to v5.0.0-beta.20 #27
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/net.dv8tion-jda-5.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-alpha.9
Update dependency net.dv8tion:JDA to v5.0.0-alpha.10
Apr 18, 2022
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
April 18, 2022 23:24
4e5a2de
to
737e793
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-alpha.10
Update dependency net.dv8tion:JDA to v5.0.0-alpha.11
Apr 25, 2022
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
April 25, 2022 20:08
737e793
to
ca37a4c
Compare
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
June 18, 2022 15:48
ca37a4c
to
4203eb5
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-alpha.11
Update dependency net.dv8tion:JDA to v5.0.0-alpha.12
Jun 18, 2022
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
September 25, 2022 22:02
4203eb5
to
deb69ee
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-alpha.12
Update dependency net.dv8tion:JDA to v5.0.0-alpha.20
Sep 25, 2022
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
November 20, 2022 20:36
deb69ee
to
2155b66
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-alpha.20
Update dependency net.dv8tion:JDA to v5.0.0-alpha.22
Nov 20, 2022
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
March 16, 2023 19:13
2155b66
to
a90a387
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-alpha.22
Update dependency net.dv8tion:JDA to v5.0.0-beta.5
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
March 20, 2023 11:13
a90a387
to
273ac3a
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-beta.5
Update dependency net.dv8tion:JDA to v5.0.0-beta.6
Mar 20, 2023
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-beta.6
Update dependency net.dv8tion:JDA to v5.0.0-beta.8
Apr 17, 2023
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
April 17, 2023 13:16
273ac3a
to
0651539
Compare
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
May 28, 2023 08:54
0651539
to
460eb6a
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-beta.8
Update dependency net.dv8tion:JDA to v5.0.0-beta.9
May 28, 2023
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
June 4, 2023 15:44
460eb6a
to
1ecae57
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-beta.9
Update dependency net.dv8tion:JDA to v5.0.0-beta.10
Jun 4, 2023
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
June 19, 2023 18:26
1ecae57
to
8b51a63
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-beta.10
Update dependency net.dv8tion:JDA to v5.0.0-beta.11
Jun 19, 2023
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
July 1, 2023 19:52
8b51a63
to
21094af
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-beta.11
Update dependency net.dv8tion:JDA to v5.0.0-beta.12
Jul 1, 2023
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
August 6, 2023 15:08
21094af
to
f98234f
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-beta.12
Update dependency net.dv8tion:JDA to v5.0.0-beta.13
Aug 6, 2023
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
September 29, 2023 17:30
f98234f
to
3864c39
Compare
renovate
bot
changed the title
Update dependency net.dv8tion:JDA to v5.0.0-beta.13
Update dependency net.dv8tion:JDA to v5.0.0-beta.14
Sep 29, 2023
renovate
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
September 30, 2023 18:03
3864c39
to
822844a
Compare
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
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
October 22, 2023 19:06
822844a
to
c070dc6
Compare
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
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
October 29, 2023 17:07
c070dc6
to
3c239d0
Compare
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
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
November 19, 2023 11:09
3c239d0
to
da4bd51
Compare
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
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
January 1, 2024 16:24
da4bd51
to
37e242a
Compare
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
bot
force-pushed
the
renovate/net.dv8tion-jda-5.x
branch
from
January 21, 2024 10:54
37e242a
to
ca13be1
Compare
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
0 participants
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:
5.0.0-alpha.8
->5.0.0-beta.20
Release Notes
DV8FromTheWorld/JDA (net.dv8tion:JDA)
v5.0.0-beta.20
: | Bug fixes and internal refactoringOverview
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
Maven
v5.0.0-beta.19
: | Bug fixes and voice channel statusOverview
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, theMANAGE_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
Maven
v5.0.0-beta.18
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
Maven
v5.0.0-beta.17
: | Fix webhooks in thread channelsOverview
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
Maven
v5.0.0-beta.16
: | Webhook Execution and Super ReactionsOverview
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(...)
ormessage.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
Maven
v5.0.0-beta.15
: | Bug fixesOverview
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
Maven
v5.0.0-beta.14
: | Media Channels, Custom Status, LRU CacheOverview
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 aForumChannel
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:
New Features
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.13...v5.0.0-beta.14
Installation
Gradle
Maven
v5.0.0-beta.13
Overview
This release includes a few bug fixes and a new
FileUpload
variant to optimize memory usage when uploading larger files.Supplier FileUpload (#2508)
With the new
FileUpload.fromStreamSupplier
, an upload will no longer retain the entire file content in memory. This comes at the cost of having to re-read the source each time.Example:
Each time the request is attempted, which can be more than once due to rate-limit retries, the supplier is used to create a new readable input stream of the file. Once the request successfully writes the entire body, the stream is closed again.
Note that the supplier must always return a new instance or reset the stream accordingly.
Getting Message Author from Reactions (#2499)
The
MessageReactionAddEvent
now provides the author id of the original message. This can be useful in situations where retrieving the message is too expensive.New Features
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.12...v5.0.0-beta.13
Installation
Gradle
Maven
v5.0.0-beta.12
: | Bug fixesOverview
This release fixes a few annoying bugs that were introduced by the username changes.
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.11...v5.0.0-beta.12
Installation
Gradle
Maven
v5.0.0-beta.11
: | Bug fixes and embed from jsonOverview
This release fixes a few issues introduced by the username changes. It also introduces
EmbedBuilder.fromData
as a way to deserialize embeds from JSON.There are also some changes to our online presence.
Create Embeds From JSON (#2471)
Using the new
EmbedBuilder.fromData
factory method, you can now create embed instances from JSON or ETF data.New Features
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.10...v5.0.0-beta.11
Installation
Gradle
Maven
v5.0.0-beta.10
Overview
With this release, we are taking the first steps to transition into the new username system for Discord by marking some methods as incubating or deprecated. This release also introduces support for AutoMod, both events and changing the AutoMod rules of a guild.
AutoMod Support (#2429)
You can now modify the AutoMod rules of a guild using
AutoModRuleData
andGuild#createAutoModRule
.Support for member profile AutoMod has not been added yet, due to the API being very unstable still.
Example
Username Changes (#2462)
Discord is changing to globally unique usernames and removing discriminators, this is explained in their blog post. We are taking the first steps to transition with this release.
Deprecated Features
Incubating Features
These are likely to be deprecated and removed in the future.
Other Changes
User#getDiscriminator
will return"0000"
for users who have a globally unique username from the new system.User#getEffectiveName
has been introduced to get the "effective display name" of a user, meaning either theUser#getGlobalName
orUser#getName
. This also affectsMember#getEffectiveName
, which will now return based on precedenceguild nickname
>global name
>username
.User#getDefaultAvatarId
now depends on the user id instead of the discriminator (when they have the discriminator 0000)New Features
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.9...v5.0.0-beta.10
Installation
Gradle
Maven
v5.0.0-beta.9
: | Bug fixes and new permissionsOverview
This release fixes a few critical bugs related to rate-limiting. We also added support for voice message receiving and new permissions relating to soundboards.
You can now use
EmbedBuilder#setUrl
to create multi-image embeds. To create multi-image embeds, simply create one embed for each image and set the same URL on all of them. The client automatically merges embeds with the same URL.Features
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.8...v5.0.0-beta.9
Installation
Gradle
Maven
v5.0.0-beta.8
: | Hotfix NullPointerExceptionOverview
This is a small hotfix release for an error introduced in beta 7.
Features
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.7...v5.0.0-beta.8
Installation
Gradle
Maven
v5.0.0-beta.7
: | Customize Rate-LimiterOverview
You can now use
RestConfig
to customize parts of the REST handling in JDA. This allows you to create custom rate-limiter implementations and make use of rate-limit proxy services such as http-proxy.Rate-Limiter Customization (#2307)
Using RestConfig, you can change parts of the REST handling. This allows you to append to the User-Agent, add custom headers, or even completely replace the existing Rate-Limiter handling:
This can also be useful to implement a different queue system for rate-limit handling. By default, JDA will always use the SequentialRateLimiter, which handles requests to the same rate-limit bucket in sequence to avoid messages being unordered. A custom implementation could replace this to run requests in parallel.
To implement a custom rate-limiter, use the existing RestRateLimiter interface and implement the required methods as documented. Your implementation will be provided with Work instances to handle.
Member Flags (#2417)
You can now access the flags on members and modify them. This allows to check if a member has rejoined the guild or passed onboarding. The rejoin flag is not entirely reliable, since Discord has only started tracking rejoins recently. Members who rejoined years ago will not have this flag set.
With
Member#modifyFlags
, you can change some of these flags. Only a subset of the existing flags are modifiable.Features
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.6...v5.0.0-beta.7
Installation
Gradle
Maven
v5.0.0-beta.6
: | Messages in Stage ChannelsOverview
This release adds support for messages and interactions inside stage channels.
New Features
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.5...v5.0.0-beta.6
Installation
Gradle
Maven
v5.0.0-beta.5
: | Hotfix voice connection issuesOverview
This is a minor release with some important bug fixes. All bots relying on voice connections should apply this update as soon as possible.
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.4...v5.0.0-beta.5
Installation
Gradle
Maven
v5.0.0-beta.4
: | Audit Log Events and Silent MessagesOverview
This release adds support for recent Discord features, such as linked roles and silent messages. We also improved the user experience for shutting down, which should come in handy for anyone building reloadable plugins.
Add GuildAuditLogEntryCreateEvent (#2380)
Discord has finally introduced an event for new audit log entries. This can be used for keeping track of all kinds of moderation relevant activity in a guild. However, to receive this event you must have the View Audit Logs permission and enable the
GUILD_MODERATION
intent (formerlyGUILD_BANS
).Silent Messages (#2392)
You can now send and receive messages which do not trigger desktop and mobile push notifications. This is done in the client by prefixing a message with
@silent
. In JDA you can usesetSuppressedNotifications(true)
to achieve the same. Note that@silent
is not the correct way to create these messages with a bot, as it is a client only feature.You can check the release pull request for more information: discord/discord-api-docs#5910
Await Shutdown (#2269)
The shutdown logic has adapted to allow more consistent behavior. We've introduced
jda.awaitShutdown()
as a way to allow blocking until all JDA subsystems reach completion. Note that this might take a long time, depending on how long your RestAction queue is at the time.The recommended way to gracefully shutdown is to define a maximum wait threshold and use it to cancel requests after some time:
In order to save CPU time, we make use of conditional variables for all of our wait loops internally. This is much more efficient than using sleep polling, like suggested in the past.
New Features
SUPPRESS_NOTIFICATIONS
flag for message by @Mysterious-Dev in https://github.com/DV8FromTheWorld/JDA/pull/2393Changes
Full Changelog: discord-jda/JDA@v5.0.0-beta.3...v5.0.0-beta.4
Installation
Gradle
Maven
v5.0.0-beta.3
Overview
Small release to fix a few bugs and introduce support for new API features.
GIF Sticker Support
Discord is adding support to create stickers with GIFs in the future. This release already covers support for receiving and creating them in advance of the rollout. Note that it will currently not work since the API for GIF stickers has not yet been deployed, in the meantime you will receive an invalid asset error.
Reverse Audit-Log Iteration
You can now use
PaginationAction#reverse
onGuild#retrieveAuditLogs
. This allows you to iterate from the oldest entry to the newest one.Removing Options/Subcommands from SlashCommands
You can now use conditional remove operations on
SlashCommandData
to remove options and slash commands.Example:
Note: You still have to pass this updated command to discord using
upsertCommand
orupdateCommands
!New Features
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.2...v5.0.0-beta.3
Installation
Gradle
Maven
v5.0.0-beta.2
Overview
Small release to fix a few bugs and typing issues.
Support for Welcome Screens (#2264 / #1989)
You can now retrieve and manage the welcome screen of a guild. To modify a welcome screen, you can use Guild#modifyWelcomeScreen:
New Features
Changes
Bug Fixes
Full Changelog: discord-jda/JDA@v5.0.0-beta.1...v5.0.0-beta.2
Installation
Gradle
Maven
v5.0.0-beta.1
: | Time to updateOverview
We finally made it 🎉 BETA 🎉 ! This concludes the major rewrites and large breaking changes of JDA version 5. With this release, we feel confident that people can rely on updates no longer requiring major rewrites of their codebases in the foreseeable future (praying to the API gods).
There will likely be some effort made to provide a full migration guide for anyone still stuck on version 4. It is recommended to update to version 5 as soon as possible. Version 4 is officially reaching EOL in the first quarter of 2023, and will stop working soon after due to the gateway version 8 being discontinued.
You can join our discord server, where we have a channel called #jda5-changes with a brief changelog for all the breaking changes.
We've also started accepting donations via Open Collective. Any donation are greatly appreciated.
Age-Restricted Commands (#2325)
You can now create NSFW (or age-restricted) commands, which are only usable in age-restricted channels.
Channel Ordering (#2320)
The implementation for
GuildChannel#compareTo
has been adjusted to support comparing channels of different types. This can be used to figure out the order of channels within the channel list. For instance, if you compare a channel to the category it is in, it will be ordered lower than the category.This also extends to
Guild#getChannels
, which now uses the updatedcompareTo
implementation for ordering. As such, you can also order a sublist of all channels yourself, by usinglist.sort()
. This even works with thread channels.New Features
Changes
Bug Fixes
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.
This PR has been generated by Mend Renovate. View repository job log here.