[dependabot]

Bumps the gradle-dependencies group with 5 updates:

Package	From	To
net.dv8tion:JDA	6.5.0	6.7.0
com.fasterxml.jackson.core:jackson-databind	2.22.2	2.22.3
ch.qos.logback:logback-classic	1.6.3	1.6.4
org.projectlombok:lombok	1.18.46	1.18.48
gradle-wrapper	9.7.1	9.8.0

Updates net.dv8tion:JDA from 6.5.0 to 6.7.0

Release notes

Sourced from net.dv8tion:JDA's releases.

v6.7.0 | Handle Channel Obfuscation

Overview

This release makes JDA aware of Channel Obfuscation, which will become mandatory on November 16, 2026.

You can test your bot early by enabling channel obfuscation in the discord developer portal.

[!WARNING] This is a breaking change, which affects permission handling and what will be available to your bot. Please report any bugs / unexpected results you might encounter with JDA behavior.

Channels for interactions will use snapshots of the channel instead, utilizing the IDetachableEntity handling previously introduced for user-installed commands. These channels carry the current information about the channel, such as name and topic. They also have the permissions for the member that used the interaction, to allow permission checks to still work as expected for that specific member through member.hasPermission(channel, permissions).

Breaking Changes

• Add handling for obfuscated channels by @​MinnDevelopment in discord-jda/JDA#3042

Full Changelog: discord-jda/JDA@v6.6.0...v6.7.0

Installation

Gradle

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

Maven

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

v6.6.0

Overview

This is a minor release adding a few new features before a bigger change coming in 6.7.0 which will introduce handling for Obfuscated Channels.

If you can, please try out and give feedback on [Add handling for obfuscated channels #3042](discord-jda/JDA#3042). To enable obfuscated channels early for testing purposes, you can toggle a switch in your application dashboard as described here.

... (truncated)

Commits

• 7c90001 Bump version to 6.7.0 (#3152)
• fe4afe4 Add handling for obfuscated channels (#3042)
• a21e38a Update dependencies (#3151)
• f4a3930 Bump the github-actions group across 1 directory with 2 updates (#3150)
• 456434e Bump version to 6.6.0 (#3143)
• 045e808 Update dependencies (#3144)
• e990a1f Fix icon URLs for GIF stickers (#3140)
• 7046c19 Fix MarkdownUtil#monospace not correctly applying monospace formatting to s...
• e1b59d8 Bump the github-actions group with 2 updates (#3141)
• f2aa674 Update Message.MAX_FILE_SIZE to 20 MiB (#3142)
• Additional commits viewable in compare view

Updates com.fasterxml.jackson.core:jackson-databind from 2.22.2 to 2.22.3

Commits

• 4385c5f [maven-release-plugin] prepare release jackson-databind-2.22.3
• ccb4fd0 Prep for 2.22.3 release
• 2958412 Merge branch '2.21' into 2.22
• 1215b94 Post-release dep version bump
• 1f0df62 [maven-release-plugin] prepare for next development iteration
• 13a9ff4 [maven-release-plugin] prepare release jackson-databind-2.21.7
• d168f96 Prep for 2.21.7 release
• eaf5c76 Merge branch '2.21' into 2.22
• e05ef4c Merge branch '2.20' into 2.21
• f6d4000 Merge branch '2.19' into 2.20
• Additional commits viewable in compare view

Updates ch.qos.logback:logback-classic from 1.6.3 to 1.6.4

Release notes

Sourced from ch.qos.logback:logback-classic's releases.

Logback 1.6.4

2026-09-24 Release of logback version 1.6.4

• Variable substitution is again applied to the scan attribute of the <configuration> element. The scanning refactoring in version 1.5.27 had dropped substitution, so values such as ${logback.scan.enabled:-true} were no longer resolved. As before version 1.5.27, an unrecognized non-empty value turns scanning on. The same substitution now applies to the scan attribute of <propertiesConfigurator>. This regression was reported in issues/1065 by vaibhavjain2.

• OutputStreamAppender and FileAppender now handle stateful encoders. The Encoder interface has a new default method called isStateful(), which returns false. An encoder that keeps state between calls to encode() can return true. For such encoders, the appender holds its write lock while encoding and while writing, so the output of concurrent appends cannot interleave. Stateless encoders still encode outside the lock, so their performance does not change. Existing encoders need no changes.

• Several race conditions in OutputStreamAppender and FileAppender were fixed. The appender is now marked started and the encoder header is written while the same lock is held, so a concurrent append can no longer write an event before the header. After acquiring the lock, the appender checks again whether it has been stopped, so no event is written after the footer. In prudent mode, FileAppender now encodes and writes each event while holding the lock.

• Fixed a data race on the logger count in LoggerContext. Loggers are created under the lock of their parent logger, so loggers with different parents could be created at the same time and increments of the shared counter could be lost. As a result, LoggerContext.size() could return a value lower than the actual number of loggers. The counter is now an AtomicInteger. This issue was reported in issues/1038 by hcantunc. The fix was contributed in PR #1055 by seonwoo_jung.

• TimeBasedRollingPolicy now supports half-day periods. Date patterns with the AM/PM marker, for example %d{yyyy-MM-dd-a}, used to be detected as daily and rolled over only at midnight. They now roll over at both 00:00 and 12:00. This issue was reported in issues/976 by shakthifuture. The fix was contributed in PR #1051 by seonwoo_jung. See TimeBasedRollingPolicy.

• If org.jline.jansi.AnsiConsole cannot be found on the class path, JansiConsoleAppender now emits warnings that explain how to add org.jline:jansi-core and then writes to the plain console stream. See codes.html#missingJlineJansi.

• The unused ch.qos.logback.classic.util.LogbackMDCAdapterSimple class was removed. LogbackMDCAdapter remains the default MDC adapter.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit 07d291ca0d280bc5da934ec9ff5f1da634fd7937 associated with the tag v_1.6.4. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Full Changelog: qos-ch/logback@v_1.6.3...v_1.6.4

Commits

• 07d291c preapre release 1.6.4
• 9627daf revert to Collections.unmodifiableMap instead of
• aa42fb5 disabled RollingCalendarTest#testVaryingNumberOfHalfDailyPeriods to shave off...
• ddc7459 Support HALF_DAY periodicity for AM/PM date patterns
• 42d75d7 disable LoggerContextTest#concurrentGetLoggerKeepsSizeConsistent to shave exe...
• bffd55e add warnings about missing jline.jansi classes
• 8de0b9b Fix data race on LoggerContext.size (#1038)
• 76c73d1 add MinimalUnmodifiableMap and return it in LogbackMDCAdapter#getPropertyMap
• a2c416a Fix formatting of email instruction in README
• 2c89727 mailing lists have been deactivated
• Additional commits viewable in compare view

Updates org.projectlombok:lombok from 1.18.46 to 1.18.48

Changelog

Sourced from org.projectlombok:lombok's changelog.

v1.18.48 (September 1st, 2026)

• BREAKING CHANGE/BUGFIX: @Builder(builderClassName = "Builder") now generates an error, because the type names collide. #3857 (found after release)
• PLATFORM: JDK27 support added #4072.
• BUGFIX: @SneakyThrows usage on JDK26 no longer results in class files that require lombok.jar to be on the runtime classpath (which should not be neccessary). #4040.
• FEATURE: New config key lombok.checkReturnValueAnnotation (values: none, lombok; default: none) lets lombok generate @lombok.CheckReturnValue on generated methods where the return value should not be ignored, such as @With methods and @Builder.build(). A future lombok release may flip the default to lombok. #4013.
• PROMOTION: @SuperBuilder has been promoted to the main package. Otherwise, no changes have been made to the annotation. The old experimental annotation will remain for a few versions, at which point it will be marked as a deprecated annotation. Eventually it'll be removed. If you had lombok.config configuration for this annotation, the configuration keys for this feature have been renamed. #2209.
• OLD-CRUFT: lombok.experimental.Wither and lombok.Delegate are deprecated remnants; these features were moved (to respectively lombok.With and lombok.experimental.Delegate over 5 years ago. They are now removed entirely. If your project is dependent on an older version of lombok which still has those; fret not, lombok still processes these annotations. It just no longer includes them in the jar.
• FEATURE: CheckerFramework: Lombok now adds @SideEffectFree to constructors it makes if you have enabled checker framework via lombok.config.
• BUGFIX: CheckerFramework: Lombok would add @SideEffectFree to the build() method of any generated builder, even if it is a builder for invoking a method; in that case, the side-effect-free nature of build() mirrors the side-effect-free nature of the method invocation you've built. Lombok now checks if the method it generated a builder for is side effect free / 'check return type'.

Commits

• b48657c [version] pre-release version bump v1.18.48
• d1d0039 Merge branch 'jdk27'
• 1a23dad [review][refactor] No meaningful changes: Improved comments, javadoc, and cle...
• 40cdde8 [changelog] JDK27 support
• 25eae29 Add Danish Nawab to AUTHORS
• 10ab92b Support JDK27: end positions moved from EndPosTable to JCTree.endpos
• af01b7a Document the new configuration syntax for listy things
• 1be3857 There is no more HtAccess
• 405985d Semantic sections for website
• 04b7340 [trivial] fixing some outdated tests (tests were broken, not lombok).
• Additional commits viewable in compare view

Updates gradle-wrapper from 9.7.1 to 9.8.0

Release notes

Sourced from gradle-wrapper's releases.

9.8.0

The Gradle team is excited to announce Gradle 9.8.0.

Here are the highlights of this release:

• Java 27 support
• Maven mirror settings reuse
• Linked problem locations in build output

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle: Aman Gautam, Björn Kautler, Eng Zer Jun, Hashim Khan, Julian Krannich, KBS, Labh R Jethe, Mark Dodgson, Maxim, monkey, nataphon-ktsystems, Paul King, Qiu Tian, rg_sandesh, Roberto Perez Alcolea, Sean, Zongle Wang.

Upgrade instructions

Switch your build to use Gradle 9.8.0 by updating your wrapper:

./gradlew :wrapper --gradle-version=9.8.0 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

9.8.0 RC3

The Gradle team is excited to announce Gradle 9.8.0 RC3.

Here are the highlights of this release:

... (truncated)

Commits

• a927be5 Add the Develocity plugin back to the Android smoke tests (#39273)
• eaee500 Add the Develocity plugin back to the Android smoke tests
• 189b672 Route everything still hitting Maven Central through the mirror (#39257)
• 36b1814 Add back mavenCentral to doc snippets
• 2740c2d Update Gradle wrapper to version 9.8.0-rc-3 (#39264)
• 2099383 Update Gradle wrapper to version 9.8.0-rc-3
• c80202f Route everything still hitting Maven Central through the mirror
• 3f6a534 Fix when a best practice was introduced (#39253)
• 9efc9ed Fix when a best practice was introduced
• 459e143 Route integration test dependencies through the repository mirror (#39239)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions