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

chore(deps): update all non-major dependencies (minor) #189

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update all non-major dependencies (minor) #189

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 16, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
actions/cache action minor v4.0.0 -> v4.1.2
docker/build-push-action action minor v6.3.0 -> v6.9.0
docker/login-action action minor v3.0.0 -> v3.3.0
itertools dependencies minor 0.11.0 -> 0.13.0
lazy_static dependencies minor 1.4.0 -> 1.5.0
regex dependencies minor 1.9.6 -> 1.11.1
serenity dependencies minor 0.11.6 -> 0.12.0
tokio (source) dependencies minor 1.31.0 -> 1.41.1

Release Notes

actions/cache (actions/cache)

v4.1.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v4...v4.1.2

v4.1.1

Compare Source

What's Changed

Full Changelog: actions/cache@v4.1.0...v4.1.1

v4.1.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v4.0.2...v4.1.0

v4.0.2

Compare Source

v4.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v4...v4.0.1

docker/build-push-action (docker/build-push-action)

v6.9.0

Compare Source

Full Changelog: docker/build-push-action@v6.8.0...v6.9.0

v6.8.0

Compare Source

Full Changelog: docker/build-push-action@v6.7.0...v6.8.0

v6.7.0

Compare Source

v6.6.1

Compare Source

Full Changelog: docker/build-push-action@v6.6.0...v6.6.1

v6.6.0

Compare Source

v6.5.0

Compare Source

v6.4.1

Compare Source

v6.4.0

Compare Source

Full Changelog: docker/build-push-action@v6.3.0...v6.4.0

docker/login-action (docker/login-action)

v3.3.0

Compare Source

Full Changelog: docker/login-action@v3.2.0...v3.3.0

v3.2.0

Compare Source

Full Changelog: docker/login-action@v3.1.0...v3.2.0

v3.1.0

Compare Source

Full Changelog: docker/login-action@v3.0.0...v3.1.0

rust-itertools/itertools (itertools)

v0.13.0

Compare Source

Breaking
  • Removed implementation of DoubleEndedIterator for ConsTuples (#​853)
  • Made MultiProduct fused and fixed on an empty iterator (#​835, #​834)
  • Changed iproduct! to return tuples for maxi one iterator too (#​870)
  • Changed PutBack::put_back to return the old value (#​880)
  • Removed deprecated repeat_call, Itertools::{foreach, step, map_results, fold_results} (#​878)
  • Removed TakeWhileInclusive::new (#​912)
Added
  • Added Itertools::{smallest_by, smallest_by_key, largest, largest_by, largest_by_key} (#​654, #​885)
  • Added Itertools::tail (#​899)
  • Implemented DoubleEndedIterator for ProcessResults (#​910)
  • Implemented Debug for FormatWith (#​931)
  • Added Itertools::get (#​891)
Changed
  • Deprecated Itertools::group_by (renamed chunk_by) (#​866, #​879)
  • Deprecated unfold (use std::iter::from_fn instead) (#​871)
  • Optimized GroupingMapBy (#​873, #​876)
  • Relaxed Fn bounds to FnMut in diff_with, Itertools::into_group_map_by (#​886)
  • Relaxed Debug/Clone bounds for MapInto (#​889)
  • Documented the use_alloc feature (#​887)
  • Optimized Itertools::set_from (#​888)
  • Removed badges in README.md (#​890)
  • Added "no-std" categories in Cargo.toml (#​894)
  • Fixed Itertools::k_smallest on short unfused iterators (#​900)
  • Deprecated Itertools::tree_fold1 (renamed tree_reduce) (#​895)
  • Deprecated GroupingMap::fold_first (renamed reduce) (#​902)
  • Fixed Itertools::k_smallest(0) to consume the iterator, optimized Itertools::k_smallest(1) (#​909)
  • Specialized Combinations::nth (#​914)
  • Specialized MergeBy::fold (#​920)
  • Specialized CombinationsWithReplacement::nth (#​923)
  • Specialized FlattenOk::{fold, rfold} (#​927)
  • Specialized Powerset::nth (#​924)
  • Documentation fixes (#​882, #​936)
  • Fixed assert_equal for iterators longer than i32::MAX (#​932)
  • Updated the must_use message of non-lazy KMergeBy and TupleCombinations (#​939)
Notable Internal Changes
  • Tested iterator laziness (#​792)
  • Created CONTRIBUTING.md (#​767)

v0.12.1

Compare Source

Added
  • Documented iteration order guarantee for Itertools::[tuple_]combinations (#​822)
  • Documented possible panic in iterate (#​842)
  • Implemented Clone and Debug for Diff (#​845)
  • Implemented Debug for WithPosition (#​859)
  • Implemented Eq for MinMaxResult (#​838)
  • Implemented From<EitherOrBoth<A, B>> for Option<Either<A, B>> (#​843)
  • Implemented PeekingNext for RepeatN (#​855)
Changed
  • Made CoalesceBy lazy (#​801)
  • Optimized Filter[Map]Ok::next, Itertools::partition, Unique[By]::next[_back] (#​818)
  • Optimized Itertools::find_position (#​837)
  • Optimized Positions::next[_back] (#​816)
  • Optimized ZipLongest::fold (#​854)
  • Relaxed Debug bounds for GroupingMapBy (#​860)
  • Specialized ExactlyOneError::fold (#​826)
  • Specialized Interleave[Shortest]::fold (#​849)
  • Specialized MultiPeek::fold (#​820)
  • Specialized PadUsing::[r]fold (#​825)
  • Specialized PeekNth::fold (#​824)
  • Specialized Positions::[r]fold (#​813)
  • Specialized PutBackN::fold (#​823)
  • Specialized RepeatN::[r]fold (#​821)
  • Specialized TakeWhileInclusive::fold (#​851)
  • Specialized ZipLongest::rfold (#​848)
Notable Internal Changes

v0.12.0

Compare Source

Breaking
  • Made take_while_inclusive consume iterator by value (#​709)
  • Added Clone bound to Unique (#​777)
Added
  • Added Itertools::try_len (#​723)
  • Added free function sort_unstable (#​796)
  • Added GroupMap::fold_with (#​778, #​785)
  • Added PeekNth::{peek_mut, peek_nth_mut} (#​716)
  • Added PeekNth::{next_if, next_if_eq} (#​734)
  • Added conversion into (Option<A>,Option<B>) to EitherOrBoth (#​713)
  • Added conversion from Either<A, B> to EitherOrBoth<A, B> (#​715)
  • Implemented ExactSizeIterator for Tuples (#​761)
  • Implemented ExactSizeIterator for (Circular)TupleWindows (#​752)
  • Made EitherOrBoth<T> a shorthand for EitherOrBoth<T, T> (#​719)
Changed
  • Added missing #[must_use] annotations on iterator adaptors (#​794)
  • Made Combinations lazy (#​795)
  • Made Intersperse(With) lazy (#​797)
  • Made Permutations lazy (#​793)
  • Made Product lazy (#​800)
  • Made TupleWindows lazy (#​602)
  • Specialized Combinations::{count, size_hint} (#​729)
  • Specialized CombinationsWithReplacement::{count, size_hint} (#​737)
  • Specialized Powerset::fold (#​765)
  • Specialized Powerset::count (#​735)
  • Specialized TupleCombinations::{count, size_hint} (#​763)
  • Specialized TupleCombinations::fold (#​775)
  • Specialized WhileSome::fold (#​780)
  • Specialized WithPosition::fold (#​772)
  • Specialized ZipLongest::fold (#​774)
  • Changed {min, max}_set* operations require alloc feature, instead of std (#​760)
  • Improved documentation of tree_fold1 (#​787)
  • Improved documentation of permutations (#​724)
  • Fixed typo in documentation of multiunzip (#​770)
Notable Internal Changes
rust-lang-nursery/lazy-static.rs (lazy_static)

v1.5.0

Compare Source

rust-lang/regex (regex)

v1.11.1

Compare Source

===================
This is a new patch release of regex that fixes compilation on nightly
Rust when the unstable pattern crate feature is enabled. Users on nightly
Rust without this feature enabled are unaffected.

Bug fixes:

  • BUG #​1231:
    Fix the Pattern trait implementation as a result of nightly API breakage.

v1.11.0

Compare Source

===================
This is a new minor release of regex that brings in an update to the
Unicode Character Database. Specifically, this updates the Unicode data
used by regex internally to the version 16 release.

New features:

v1.10.6

Compare Source

===================
This is a new patch release with a fix for the unstable crate feature that
enables std::str::Pattern trait integration.

Bug fixes:

  • BUG #​1219:
    Fix the Pattern trait implementation as a result of nightly API breakage.

v1.10.5

Compare Source

===================
This is a new patch release with some minor fixes.

Bug fixes:

  • BUG #​1203:
    Escape invalid UTF-8 when in the Debug impl of regex::bytes::Match.

v1.10.4

Compare Source

===================
This is a new patch release with some minor fixes.

  • BUG #​1169:
    Fixes a bug with compiling a reverse NFA automaton in regex-automata.
  • BUG #​1178:
    Clarifies that when Cow::Borrowed is returned from replace APIs, it is
    equivalent to the input.

v1.10.3

Compare Source

===================
This is a new patch release that fixes the feature configuration of optional
dependencies, and fixes an unsound use of bounds check elision.

Bug fixes:

  • BUG #​1147:
    Set default-features=false for the memchr and aho-corasick dependencies.
  • BUG #​1154:
    Fix unsound bounds check elision.

v1.10.2

Compare Source

===================
This is a new patch release that fixes a search regression where incorrect
matches could be reported.

Bug fixes:

  • BUG #​1110:
    Revert broadening of reverse suffix literal optimization introduced in 1.10.1.

v1.10.1

Compare Source

===================
This is a new patch release with a minor increase in the number of valid
patterns and a broadening of some literal optimizations.

New features:

  • FEATURE 04f5d7be:
    Loosen ASCII-compatible rules such that regexes like (?-u:☃) are now allowed.

Performance improvements:

  • PERF 8a8d599f:
    Broader the reverse suffix optimization to apply in more cases.

v1.10.0

Compare Source

===================
This is a new minor release of regex that adds support for start and end
word boundary assertions. That is, \< and \>. The minimum supported Rust
version has also been raised to 1.65, which was released about one year ago.

The new word boundary assertions are:

  • \< or \b{start}: a Unicode start-of-word boundary (\W|\A on the left,
    \w on the right).
  • \> or \b{end}: a Unicode end-of-word boundary (\w on the left, \W|\z
    on the right)).
  • \b{start-half}: half of a Unicode start-of-word boundary (\W|\A on the
    left).
  • \b{end-half}: half of a Unicode end-of-word boundary (\W|\z on the
    right).

The \< and \> are GNU extensions to POSIX regexes. They have been added
to the regex crate because they enjoy somewhat broad support in other regex
engines as well (for example, vim). The \b{start} and \b{end} assertions
are aliases for \< and \>, respectively.

The \b{start-half} and \b{end-half} assertions are not found in any
other regex engine (although regex engines with general look-around support
can certainly express them). They were added principally to support the
implementation of word matching in grep programs, where one generally wants to
be a bit more flexible in what is considered a word boundary.

New features:

Performance improvements:

  • PERF #​1051:
    Unicode character class operations have been optimized in regex-syntax.
  • PERF #​1090:
    Make patterns containing lots of literal characters use less memory.

Bug fixes:

  • BUG #​1046:
    Fix a bug that could result in incorrect match spans when using a Unicode word
    boundary and searching non-ASCII strings.
  • BUG(regex-syntax) #​1047:
    Fix panics that can occur in Ast->Hir translation (not reachable from regex
    crate).
  • BUG(regex-syntax) #​1088:
    Remove guarantees in the API that connect the u flag with a specific HIR
    representation.

regex-automata breaking change release:

This release includes a regex-automata 0.4.0 breaking change release, which
was necessary in order to support the new word boundary assertions. For
example, the Look enum has new variants and the LookSet type now uses u32
instead of u16 to represent a bitset of look-around assertions. These are
overall very minor changes, and most users of regex-automata should be able
to move to 0.4 from 0.3 without any changes at all.

regex-syntax breaking change release:

This release also includes a regex-syntax 0.8.0 breaking change release,
which, like regex-automata, was necessary in order to support the new word
boundary assertions. This release also includes some changes to the Ast
type to reduce heap usage in some cases. If you are using the Ast type
directly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7 should be able to migrate to 0.8 without any code changes.

regex-lite release:

The regex-lite 0.1.1 release contains support for the new word boundary
assertions. There are no breaking changes.

serenity-rs/serenity (serenity)

v0.12.2

Compare Source

Thanks to the following for their contributions:

Deprecations

Continuing with the deprecations started in 0.12.1, many more methods and fields have been deprecated in order to make an easier upgrade path to 0.13.

These deprecation messages include a migration path, it is recommended to go one by one using cargo check and migrate each warning to reduce the burden migrating to 0.13. Following is a list of the deprecation PRs and the justification for these changes.

  • (#​2791) The Channel::is_nsfw method was wrong, useless, and served better by GuildChannel::nsfw
  • (#​2794) These cache methods needed arcane borrow checker dances internally, and obscure the simplicity of the cache.
  • (#​2816) Member::highest_role_info is now strictly less powerful than the new Guild::member_highest_role and can avoid a cache lookup if used correctly.
  • (#​2825)
    • Guild::is_large is less accurate than Guild::large
    • Message::is_own is super simple to implement yourself
    • Message::is_private simply checks if Message::guild_id is none.
  • (#​2838) Event::PresencesReplace does not exist, and is a relic from when serenity supported user accounts.
  • (#​2861) TeamMember::permissions is always ["*"], so is useless.
Other notable changes
  • (#​2790) Added CreateMessage::enforce_nonce, to prevent sending duplicate messages.
  • (#​2801) Added EditProfile::banner, allowing banners to be set for bots.
  • (#​2810) Added ChannelId::get_thread_member.
  • (#​2812) Added Guild::partial_member_permissions_in, which can be used to avoid fetching a Member in message events just to check permissions.
  • (#​2819) Added From<User> for CreateEmbedAuthor, setting the author name and icon to the User's info.
  • (#​2813) Added UserId::direct_message, so you don't need a full User to direct message.
  • (#​2834) Added Http::default_allowed_mentions to set the AllowedMentions to be used with every request.
  • (#​2830) Added Guild(Id)::bulk_ban, allowing bulk banning without hitting rate limits.
  • (#​2836) Added support for Message Polls, including reading and sending them.
  • (#​2807) Added support for User Apps, alllowing user-installable application commands.
  • (#​2882) Added support for super reactions.
  • Many documentation fixes and other optimisations to improve memory and CPU usage.

v0.12.1

Compare Source

Thanks to the following for their contributions:

Notable changes

In this release, the standard framework has been deprecated
(#​2733).

As Discord continues to endorse and evolve application commands (/...
commands, user commands, message commands, etc.), the standard framework
becomes increasingly outdated. Bots are also steadily losing (and already have
lost) access to contents of messages, making it difficult to build a
prefix-only bot. Unless you plan on restricting your bot to only accept
commands in DMs, allowing its presence in only fewer than 100 guilds, or
presenting a reasonable justification to Discord for permission to continue
using message contents, you should migrate to application commands. We
recommend poise, which supports writing
both prefix and application commands with a #[command] macro like the
standard framework.

Why not just update the framework?

Poise already exists and is better than the standard framework. Efforts should
be directed at improving poise instead. To support application commands would
require an overhaul of the standard framework, as they are special (for
instance, Discord parses arguments on behalf of the bot and passes them as
structured data, whereas for prefix commands, the bot must parse by itself).

Smaller, but still notable changes
  • (#​2621) Add a temporary cache for messages.
  • (#​2649) Deprecate RoleId::to_role_cached - Use Guild::roles instead.
  • (#​2726) Pack bitflags - Reduces alignments of bitflags! types, resulting in a smaller memory footprint.
  • (#​2696) Support attachments in forum posts.
  • (#​2560) Add support for monetization APIs.
  • (#​2648) Deprecate inefficient Emoji helpers - Use the emoji methods on GuildId/Guild instead.

v0.12.0

Compare Source

This release turned out to be one of serenity's largest ever, with well over 300 PRs in total! It contains quite a few major breaking changes to the API. Therefore, the changelog for this release also serves as a migration guide for users upgrading from the 0.11 series.

Thanks to the following for their contributions:

Builders

The closure-based API for constructing requests using the builder pattern has been ripped out and replaced. In place of closures, users must now pass in builder types directly. For example, in serenity 0.11, code like the following was very common:

let channel = guild
    .create_channel(&http, |c| c.name("my-test-channel").kind(ChannelType::Text))
    .await?;

Now, users instead write the following code:

let builder = CreateChannel::new("my-test-channel").kind(ChannelType::Text);
let channel = guild.create_channel(&http, builder).await?;

Or, inline like so:

let channel = guild
    .create_channel(&http, CreateChannel::new("my-test-channel").kind(ChannelType::Text))
    .await?;

Note that in this particular example, the channel name is now a mandatory field that must be passed in when constructing the builder. Mutating the builder with subsequent calls to CreateChannel::name will change the underlying value. Additionally, all methods on builders now take mut self and return Self, instead of taking and returning &mut self/&mut Self. This allows for explicit construction as in the second example above. Also, builders no longer wrap a pub HashMap<&'static str, T>; the hashmap has been flattened into concrete private fields.

Some benefits to this new approach to builders are:

  1. Because every closure has a type unique to it, each call to a method taking a closure would be monomorphized separately, resulting in binary bloat. This is no longer the case.
  2. Builders can be constructed once and then cloned and re-used multiple times.
  3. Enforcement of field requirements (as dictated by the Discord API docs) provides compile-time request validation.
Attachments
  • The AttachmentType enum has been replaced with a CreateAttachment builder struct. This struct has the file, path, and url constructors that eagerly evaluate the data passed to them - CreateAttachment simply stores the resulting raw data. This is in contrast to AttachmentType which lazily carried filepaths/urls with it, and had data and filename methods for resolving them. Additionally, the CreateAttachment::to_base64 method can be used to manually encode an attachment if needed.
  • A new EditAttachments builder struct has been added for use with the attachments method on the EditMessage, EditWebhookMessage, and EditInteractionResponse builders. This new builder provides finer control when editing a message's existing attachments or uploading additional ones. Also, the following methods have been renamed to more accurately reflect their behavior:
serenity v0.11 serenity v0.12
EditMessage::attachment EditMessage::new_attachment
EditMessage::add_existing_attachment EditMessage::keep_existing_attachment
EditWebhookMessage::clear_existing_attachments EditWebhookMessage::clear_attachments
EditInteractionResponse::clear_existing_attachments EditInteractionResponse::clear_attachments
Collectors

Collectors have been redesigned and simplified at no cost to expressibility. There is now a generic collector::collect function which takes a closure as argument, letting you filter events as they stream in.

  • The specific collectors (ComponentInteractionCollector, ModalInteractionCollector, MessageCollector, and ReactionCollector) are simply convenience structs that wrap this underlying function.
  • EventCollector is now deprecated, as its use usually involved anti-patterns around fallibility. However, its functionality can still be replicated using collector::collect. See example 10 for more details.
  • The RelatedId and RelatedIdsForEventType types have been removed as they were only used by EventCollector. Methods for retrieving them from events have also been removed; if users wish to extract "related" ids from an event, they should do so directly from the event's fields. The removed methods are the following:
    • Event::user_id
    • Event::guild_id
    • Event::channel_id
    • Event::message_id
    • EventType::related_ids
Commands

In an effort to shorten long names and make import paths less unwieldy, Serenity now uses command instead of application_command in all places, except for the Permissions::USE_APPLICATION_COMMANDS constant. This includes methods on the Http, GuildId, Guild, PartialGuild, and Command types, as well as a few other miscellaneous places:

serenity v0.11 serenity v0.12
Http::*_{global,guild}_application_command* Http::*_{global,guild}_command*
{GuildId,Guild,PartialGuild}::*_application_command* {GuildId,Guild,PartialGuild}::*_command*
Command::*_global_application_command* Command::*_global_command*
Interaction::application_command Interaction::command
EventHandler::application_command_permissions_update EventHandler::command_permissions_update
Route::ApplicationCommand* Route::Command*
Permissions::use_application_commands Permissions::use_commands

Additionally, the following command types have been renamed:

serenity v0.11 serenity v0.12
CreateApplicationCommand CreateCommand
CreateApplicationCommandOption CreateCommandOption
CreateApplicationCommandPermissionData CreateCommandPermission
CreateApplicationCommandPermissionsData EditCommandPermissions
CommandPermission CommandPermissions
CommandPermissionData CommandPermission

Furthermore, the methods on CreateCommandPermission, such as new, kind, etc. have been replaced with constructors for each type of permission, e.g. role, user, channel, etc., to avoid a possible mismatch between kind and the id that gets passed in.

Finally, the {GuildId,Guild,PartialGuild}::create_command_permission method has been renamed to edit_command_permission to more accurately reflect its behavior.

Cache
  • Cache methods now return a CacheRef type that wraps a reference into the cache. Other methods that returned a map, now return a wrapper type around a reference to the map, with a limited API to prevent accidental deadlocks. This all helps reduce the number of clones when querying the cache. Those wishing to replicate the old behavior can simply call .clone() on the return type to obtain the wrapped data.
  • CacheSettings has new fields time_to_live, cache_guilds, cache_channels, and cache_users, allowing cache configuration on systems with memory requirements; whereas previously, memory-constrained systems were forced to disable caching altogether.
  • Caching for PrivateChannels (aka DM channels) has been removed, as they are never sent across the gateway by Discord. Therefore, the Cache::{private_channel, private_channels} methods have been removed, and Cache::guild_channel has been renamed to just Cache::channel. Additionally, some uses of the Channel enum in return types have been replaced with either GuildChannel or PrivateChannel as seen fit.
IDs

All *Id types have had their internal representations made private. Therefore, the API has changed as follows:

serenity v0.11 serenity v0.12
ExampleId(12345) ExampleId::new(12345)
example_id.as_u64() example_id.get()

Note that all *Id types now implement Into<u64> and Into<i64>. Additionally, attempting to instantiate an id with a value of 0 will panic.

Also, the implementations of FromStr for the UserId, RoleId, and ChannelId types now expect an integer rather than a mention string. The following table shows the new expected input strings:

serenity v0.11 serenity v0.12
ChannelId <#&#8203;81384788765712384> 81384788765712384
RoleId <@&#8203;&136107769680887808> 136107769680887808
UserId <@&#8203;114941315417899012> or <@&#8203;!114941315417899012> 114941315417899012

Users wishing to parse mentions should either parse into a Mention object, or use the utils::{parse_user_mention, parse_role_mention, parse_channel_mention} methods.

Interactions

The various interaction types have been renamed as follows:

serenity v0.11 serenity v0.12
ApplicationCommandInteraction CommandInteraction
MessageComponentInteraction ComponentInteraction
ModalSubmitInteraction ModalInteraction

Method names on interaction types have been shortened in the following way:

serenity v0.11 serenity v0.12
create_interaction_response create_response
create_followup_message create_followup
delete_original_interaction_response delete_response
delete_followup_message delete_followup
edit_original_interaction_response edit_response
edit_followup_message edit_followup
get_interaction_response get_response
get_followup_message get_followup
  • AutocompleteInteraction has been merged into CommandInteraction, along with its corresponding methods.
  • The kind field has been removed from each of the interaction structs.
  • A quick_modal method has been added to CommandInteraction and ComponentInteraction. See the docs for more details.
Framework

The standard framework is now configurable at runtime, as the configure method now takes self by reference. In line with the builder changes, the Configuration and BucketBuilder builders are no longer closure-based and must be passed in directly. Also, the Framework trait has been reworked to accomodate more use cases than just text commands:

  • The dispatch method now takes a FullEvent as argument instead of just a Message. This enum contains all the data that is passed to the EventHandler.
  • An optional init method has been added, that allows for more complex framework initialization, which can include executing HTTP requests, or accessing cache or shard data.

As a result, the trait now accomodates alternative frameworks more easily, such as poise.

Gateway
  • Renamed WsStream to WsClient.
  • The ShardManagerMonitor and ShardManagerMessage t

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 changed the title fix(deps): update rust crate tokio to 1.32.0 chore(deps): update all non-major dependencies Sep 8, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 76724c2 to 2e9b45c Compare September 8, 2023 17:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 918d81c to ed2c246 Compare October 9, 2023 22:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 0d47ec9 to 2d86f7e Compare November 14, 2023 21:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 36f480a to 0318818 Compare January 29, 2024 21:56
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies (minor) Jan 29, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from f5b1bca to 8da4510 Compare February 2, 2024 13:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from c339d94 to d2f5dd3 Compare March 8, 2024 11:01
@renovate renovate bot changed the title fix(deps): update all non-major dependencies (minor) chore(deps): update all non-major dependencies (minor) Mar 8, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4388311 to 626cbd3 Compare March 14, 2024 10:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 467df6c to 76c15a4 Compare March 28, 2024 20:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 76c15a4 to 2084133 Compare May 16, 2024 19:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2084133 to 55c6e4d Compare May 28, 2024 10:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b4bf87b to 419051b Compare June 10, 2024 09:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 419051b to 574877a Compare June 22, 2024 00:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from f30abda to 4a3e66d Compare July 17, 2024 11:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 6e85c14 to 0751708 Compare July 27, 2024 11:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 518cae1 to ea58dfb Compare August 7, 2024 22:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e6100bb to 52bda1f Compare August 17, 2024 19:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from eedf5d9 to d37a0d5 Compare August 30, 2024 09:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 21a80a1 to a566106 Compare September 30, 2024 13:21
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 7db87ee to d9355a8 Compare October 8, 2024 19:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 0ee99ce to 06c20fb Compare October 24, 2024 15:46
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.
0 participants