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.

Sign up for GitHub

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

Jump to bottom

Update all dependencies #158

Merged
merged 1 commit into from
Aug 16, 2024
Merged

Update all dependencies #158

merged 1 commit into from
Aug 16, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 27, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
actions/upload-artifact action patch v4.3.3 -> v4.3.6 age adoption passing confidence
amazoncorretto final patch 21.0.3-alpine -> 21.0.4-alpine age adoption passing confidence
gradle (source) minor 8.8 -> 8.10 age adoption passing confidence
gradle/gradle-build-action action digest 66535aa -> 093dfe9
org.apache.commons:commons-lang3 (source) dependencies minor 3.14.0 -> 3.16.0 age adoption passing confidence
org.junit.jupiter:junit-jupiter-engine (source) dependencies minor 5.10.2 -> 5.11.0 age adoption passing confidence
org.junit.jupiter:junit-jupiter-api (source) dependencies minor 5.10.2 -> 5.11.0 age adoption passing confidence
org.mariadb.jdbc:mariadb-java-client (source) dependencies patch 3.4.0 -> 3.4.1 age adoption passing confidence
com.h2database:h2 (source) dependencies minor 2.2.224 -> 2.3.232 age adoption passing confidence
io.sentry:sentry dependencies minor 7.10.0 -> 7.14.0 age adoption passing confidence
ch.qos.logback:logback-classic (source, changelog) dependencies patch 1.5.6 -> 1.5.7 age adoption passing confidence
net.dv8tion:JDA dependencies patch 5.0.0-beta.24 -> 5.0.2 age adoption passing confidence

Release Notes

actions/upload-artifact (actions/upload-artifact)

v4.3.6

Compare Source

v4.3.5

Compare Source

v4.3.4

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.3...v4.3.4

gradle/gradle (gradle)

v8.10

Compare Source

v8.9

Compare Source

mariadb-corporation/mariadb-connector-j (org.mariadb.jdbc:mariadb-java-client)

v3.4.1

Compare Source

Full Changelog

Bugs Fixed
  • CONJ-1181 Ensure Prepare cache use schema
  • CONJ-1178 DatabaseMetaData.getImportedKeys return different PK_NAME value than getExportedKeys.
  • CONJ-1180 Correct DatabaseMeta.getExportedKeys() performances
  • CONJ-1185 Android app compatibility, regex CANON_EQ flag not supported
  • CONJ-1188 database meta getSQLKeywords listing all reserved key word, not restricted keywords only
  • CONJ-1189 implementation of pinGlobalTxToPhysicalConnection for XA Connection
  • CONJ-1190 Adding MySQL option 'databaseTerm' as alias for useCatalogTerm for compatibility
  • CONJ-1191 slow metadata getImportedKeys when not having database set
  • CONJ-685 permit setting sslMode per host
  • CONJ-686 Allow mixing TCP and socket hosts in failover configuration
  • CONJ-1068 ResultSetMetaData.getColumnTypeName() returns VARCHAR instead of TINYTEXT
  • CONJ-1182 missing XA_RBTIMEOUT,XA_RBTIMEOUT and XA_RBDEADLOCK error mapping
getsentry/sentry-java (io.sentry:sentry)

v7.14.0

Compare Source

Features
  • Session Replay: Gesture/touch support for Flutter (#​3623)
Fixes
  • Fix app start spans missing from Pixel devices (#​3634)
  • Avoid ArrayIndexOutOfBoundsException on Android cpu data collection (#​3598)
  • Fix lazy select queries instrumentation (#​3604)
  • Session Replay: buffer mode improvements (#​3622)
    • Align next segment timestamp with the end of the buffered segment when converting from buffer mode to session mode
    • Persist buffer replay type for the entire replay when converting from buffer mode to session mode
    • Properly store screen names for buffer mode
  • Session Replay: fix various crashes and issues (#​3628)
    • Fix video not being encoded on Pixel devices
    • Fix SIGABRT native crashes on Xiaomi devices when encoding a video
    • Fix RejectedExecutionException when redacting a screenshot
    • Fix FileNotFoundException when persisting segment values
Chores
  • Introduce ReplayShadowMediaCodec and refactor tests using custom encoder (#​3612)

v7.13.0

Compare Source

Features
  • Session Replay: (#​3565) (#​3609)
    • Capture remaining replay segment for ANRs on next app launch
    • Capture remaining replay segment for unhandled crashes on next app launch
Fixes
  • Session Replay: (#​3565) (#​3609)
    • Fix stopping replay in session mode at 1 hour deadline
    • Never encode full frames for a video segment, only do partial updates. This further reduces size of the replay segment
    • Use propagation context when no active transaction for ANRs
Dependencies

v7.12.1

Compare Source

Fixes
  • Check app start spans time and ignore background app starts (#​3550)
    • This should eliminate long-lasting App Start transactions

v7.12.0

Compare Source

Features

  • Session Replay Public Beta (#​3339)

    To enable Replay use the sessionReplay.sessionSampleRate or sessionReplay.errorSampleRate experimental options.

    import io.sentry.SentryReplayOptions
import io.sentry.android.core.SentryAndroid

SentryAndroid.init(context) { options ->
 
  // Currently under experimental options:
  options.experimental.sessionReplay.sessionSampleRate = 1.0
  options.experimental.sessionReplay.errorSampleRate = 1.0

  // To change default redaction behavior (defaults to true)
  options.experimental.sessionReplay.redactAllImages = true
  options.experimental.sessionReplay.redactAllText = true

  // To change quality of the recording (defaults to MEDIUM)
  options.experimental.sessionReplay.quality = SentryReplayOptions.SentryReplayQuality.MEDIUM // (LOW|MEDIUM|HIGH)
}

    To learn more visit Sentry's Mobile Session Replay documentation page.

v7.11.0

Compare Source

Features
Fixes
  • Fix duplicate session start for React Native (#​3504)
  • Move onFinishCallback before span or transaction is finished (#​3459)
  • Add timestamp when a profile starts (#​3442)
  • Move fragment auto span finish to onFragmentStarted (#​3424)
  • Remove profiling timeout logic and disable profiling on API 21 (#​3478)
  • Properly reset metric flush flag on metric emission (#​3493)
  • Use SecureRandom in favor of Random for Metrics (#​3495)
  • Fix UncaughtExceptionHandlerIntegration Memory Leak (#​3398)
  • Deprecated User.segment. Use a custom tag or context instead. (#​3511)
  • Fix duplicated http spans (#​3526)
  • When capturing unhandled hybrid exception session should be ended and new start if need (#​3480)
Dependencies
discord-jda/JDA (net.dv8tion:JDA)

v5.0.2: | Single time event listener

Overview

This release includes some bug fixes as well as a new event listener feature to add a one-time-use event listener.

Once Event Listener (#​2683)

A common problem that developers run into, is "waiting" for a specific event in the context of some command. For instance, waiting for a user to add a reaction or reply with a message in response to some prompt.

This can now be achieved using the new listenOnce event listener:

// listen for a message event
jda.listenOnce(MessageReceivedEvent.class)
    // filter for specific event
    .filter(event -> event.getChannel().equals(channel))
    .filter(event -> event.getAuthor().equals(user))
    // handle timeout
    .timeout(timeout, () -> hook.editOriginal("Timeout!").queue())
    // subscribe to first event that matches filters
    .subscribe(event -> {
        hook.editOriginal("You sent: " + event.getMessage().getContentRaw()).queue();
    });

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.1...v5.0.2

Installation

Gradle

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

Maven

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

v5.0.1: | Hotfix shard manager thread handling

Overview

Small hotfix release, fixes problem with default thread config for DefaultShardManager. This caused requests to fail if a shard is stopped or restarted.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0...v5.0.1

Installation

Gradle

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

Maven

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

v5.0.0: | End of beta phase

The Long Awaited Stabilization

After almost 3 years of refactoring and polishing, the stabilization of JDA 5.0.0 is here. If you have been following along, not much has changed since the latest beta release.

If you have somehow avoided updating to a beta release since 2021, here is a list of the most noteworthy additions, changes, and bug fixes since 4.4.0.

You can also use our Migration Guide to help you update to the latest version of JDA 5. This guide also includes the most important changes you need to consider.

Interactions / Application Features

Discord has further improved the capabilities of applications with new types of interactions. This major release of JDA adds support for these features, coming with some restructuring to properly accomodate the new types.

We've renamed interaction events to a more consistent naming scheme:

  • SlashCommandEvent becomes SlashCommandInteractionEvent
  • ButtonClickEvent becomes ButtonInteractionEvent

Similarly, we've renamed component types slightly:

  • SelectionMenu is now StringSelectMenu, while adding a new EntitySelectMenu
  • What was previously called Component has now been renamed to ActionComponent and ItemComponent, allowing us to introduce Component as an abstraction over both Button and ActionRow (which is now a LayoutComponent). The new Component interface is now an abstraction over both ItemComponent and LayoutComponent.

To learn more about interactions in JDA 5, take a look at our Interactions Wiki Guide.

Channel Type Rework

We've refactored the channel types and usages in JDA to be more maintainable. Each type of channel now directly maps to a specific channel interface, unlike before where VoiceChannel was used for both stage and voice type channels.
Instead there are now concrete interfaces for each type, such as NewsChannel, StageChannel, ForumChannel, etc.

The channel type hierarchy has been further refined, by introducing higher level abstractions to represent the features of multiple channel types:

As well as more specific features or attributes of channels:

To properly maintain these many different channel types and make them easy to use, we've also introduced new union types to encompass multiple channels into a simple common union type. This replaces the old getTextChannel()/getVoiceChannel() getters on events with getChannel().asTextChannel(). However, you can also use the standard features of the unions directly. For instance, a MessageChannelUnion allows to send messages and these specialization methods:

MessageChannelUnion channel = event.getChannel();
channel.sendMessage("hello").queue();
if (channel.getType() == TEXT) {
  channel.asTextChannel().getManager().setTopic("test topic").queue();
}

Cache access has also seen some improvement, by introducing a new getChannelById(Class, long) method, allowing to just get a MessageChannel without worrying about the concrete type.

GuildMessageChannel channel = guild.getChannelById(GuildMessageChannel.class, 125227483518861312L);
channel.sendMessage("Hello general chat!").queue();

Learn more about the channel rework in Channel Rework.

Message Features

We've refactored our message sending interfaces to be more consistent, by abstracting MessageAction, MessageBuilder, and ReplyAction into shared interfaces MessageCreateRequest and MessageEditRequest. This makes all message sending code consistent. We recommend to simply chain your builder-like code directly on send messages:

channel.sendMessage("Hello World")
  .setComponents(ActionRow.of(button1, button2))
  .setEmbeds(embed1, embed2)
  .setFiles(files)
  .queue();

However, if you need to use builders, we've introduced MessageEditBuilder and MessageCreateBuilder to replace the old MessageBuilder utility. You can also now use SplitUtil to easily divide message content into multiple messages.

To support file descriptions and reduce the number of sendFile overloads, we've also introduced a new FileUpload type that unifies all attachments into a single type.

FileUpload file = FileUpload.fromData(new File("myFile.png"), "image.png")
  .setDescription("this is my alt text for screenreaders, allowing to make accessible images in your messages!");
channel.sendFiles(file).queue();

Learn more about the changes to message sending in Message Send/Edit Rework.

Emojis and Stickers

In JDA 5, we have decided to unify all emoji types into a consistent type structure:

These new emoji types replace the duplication of ReactionEmote and Activity.Emoji.

Stickers have also been refactored in a similar way, making a clear distinction between stickers found in messages and guild settings:

  • Sticker, a top-level abstraction of all sticker types
  • StickerItem, stickers found in messages
  • RichSticker, stickers with more information that is usually omitted for messages (sticker items)
  • StandardSticker, rich stickers provided by nitro instead of guilds
  • GuildSticker, rich stickers provided in guilds
  • StickerUnion, adding type casting

Learn more about the changes to emojis and stickers in Sticker and Emoji Rework.

Installation

All future JDA releases will be distributed through maven central. You no longer need to use jcenter() in your dependency manager.

Gradle

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

Maven

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

Changelog (5.0.0-beta.24 -> 5.0.0)

The changes since the latest beta release to this release.

Changelog (4.4.0 -> 5.0.0)

Note that this changelog is a linear history of changes. This means some earlier changes have already been superseded or refined in more recent changes. This changelog is slightly compressed to remove unimportant changes, you can see the full list of commits here.

Thank you all for contributing!

New Features

New feature additions since 4.4.0

Breaking Changes

Breaking changes since 4.4.0

Other Changes

Other noteworthy changes since 4.4.0

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all branch from be8b64a to 8331d7e Compare July 2, 2024 00:00
@renovate renovate bot changed the title Update all dependencies to v5.10.3 Update all dependencies Jul 2, 2024
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from 17ad79b to 2f4eea4 Compare July 11, 2024 17:05
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 8113700 to 1a720ff Compare July 18, 2024 04:29
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from e67732e to 0c5a37f Compare July 31, 2024 10:18
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 540e909 to d36b42c Compare August 8, 2024 01:59
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from 8c6a5cb to ae16a87 Compare August 14, 2024 13:11
@vLuckyyy vLuckyyy merged commit 37ba965 into master Aug 16, 2024
3 checks passed
@vLuckyyy vLuckyyy deleted the renovate/all branch August 16, 2024 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
1 participant
@vLuckyyy