fix(deps): update all non-major dependencies (minor) #189
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
76724c2 to
2e9b45c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
918d81c to
ed2c246
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
ed2c246 to
720fd21
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
0d47ec9 to
2d86f7e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
2d86f7e to
b242f6e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
b242f6e to
41dc10f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
41dc10f to
163a34a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
163a34a to
fa1680b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
fa1680b to
758408a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
36f480a to
0318818
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
f5b1bca to
8da4510
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
8da4510 to
c339d94
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
c339d94 to
d2f5dd3
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
4388311 to
626cbd3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
467df6c to
76c15a4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
76c15a4 to
2084133
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
2084133 to
55c6e4d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
8c58d2f to
e3cf25f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
6e85c14 to
0751708
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
518cae1 to
ea58dfb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
e6100bb to
52bda1f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
eedf5d9 to
d37a0d5
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
d37a0d5 to
38cfc02
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
21a80a1 to
a566106
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
7db87ee to
d9355a8
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
0ee99ce to
06c20fb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
06c20fb to
c857bd6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
dfa775a to
3e2be3a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
3e2be3a to
fbde259
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
fbde259 to
0fc0554
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
0fc0554 to
668e5a7
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
v4.0.0->v4.2.0v6.3.0->v6.10.0v3.0.0->v3.3.00.11.0->0.13.01.4.0->1.5.01.9.6->1.11.10.11.6->0.12.01.31.0->1.42.0Release Notes
actions/cache (actions/cache)
v4.2.0Compare Source
The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.
The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.
We are deprecating some versions of this action. We recommend upgrading to version
v4orv3as soon as possible before February 1st, 2025. (Upgrade instructions below).If you are using pinned SHAs, please use the SHAs of versions
v4.2.0orv3.4.0If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.
Upgrading to the recommended versions will not break your workflows.
Read more about the change & access the migration guide: reference to the announcement.
Minor changes
Minor and patch version updates for these dependencies:
1.11.11.1.30.38.3Full Changelog: actions/cache@v4...v4.2.0
v4.1.2Compare Source
What's Changed
isGheslogic by @jww3 in https://github.com/actions/cache/pull/14744.1.2release by @Link- in https://github.com/actions/cache/pull/1477New Contributors
Full Changelog: actions/cache@v4...v4.1.2
v4.1.1Compare Source
What's Changed
cache-hitoutput by @joshmgross in https://github.com/actions/cache/pull/1467Full Changelog: actions/cache@v4.1.0...v4.1.1
v4.1.0Compare Source
What's Changed
save-alwaysinput by @joshmgross in https://github.com/actions/cache/pull/1452New Contributors
Full Changelog: actions/cache@v4.0.2...v4.1.0
v4.0.2Compare Source
v4.0.1Compare Source
What's Changed
New Contributors
Full Changelog: actions/cache@v4...v4.0.1
docker/build-push-action (docker/build-push-action)
v6.10.0Compare Source
callinput to set method for evaluating build by @crazy-max in https://github.com/docker/build-push-action/pull/1265Full Changelog: docker/build-push-action@v6.9.0...v6.10.0
v6.9.0Compare Source
Full Changelog: docker/build-push-action@v6.8.0...v6.9.0
v6.8.0Compare Source
Full Changelog: docker/build-push-action@v6.7.0...v6.8.0
v6.7.0Compare Source
v6.6.1Compare Source
Full Changelog: docker/build-push-action@v6.6.0...v6.6.1
v6.6.0Compare Source
v6.5.0Compare Source
v6.4.1Compare Source
v6.4.0Compare Source
repositoryandghtokenattributes for GitHub Actions cache backend by @crazy-max in https://github.com/docker/build-push-action/pull/1133Full Changelog: docker/build-push-action@v6.3.0...v6.4.0
docker/login-action (docker/login-action)
v3.3.0Compare Source
Full Changelog: docker/login-action@v3.2.0...v3.3.0
v3.2.0Compare Source
Full Changelog: docker/login-action@v3.1.0...v3.2.0
v3.1.0Compare Source
Full Changelog: docker/login-action@v3.0.0...v3.1.0
rust-itertools/itertools (itertools)
v0.13.0Compare Source
Breaking
DoubleEndedIteratorforConsTuples(#853)MultiProductfused and fixed on an empty iterator (#835, #834)iproduct!to return tuples for maxi one iterator too (#870)PutBack::put_backto return the old value (#880)repeat_call, Itertools::{foreach, step, map_results, fold_results}(#878)TakeWhileInclusive::new(#912)Added
Itertools::{smallest_by, smallest_by_key, largest, largest_by, largest_by_key}(#654, #885)Itertools::tail(#899)DoubleEndedIteratorforProcessResults(#910)DebugforFormatWith(#931)Itertools::get(#891)Changed
Itertools::group_by(renamedchunk_by) (#866, #879)unfold(usestd::iter::from_fninstead) (#871)GroupingMapBy(#873, #876)Fnbounds toFnMutindiff_with, Itertools::into_group_map_by(#886)Debug/Clonebounds forMapInto(#889)use_allocfeature (#887)Itertools::set_from(#888)README.md(#890)Cargo.toml(#894)Itertools::k_smalleston short unfused iterators (#900)Itertools::tree_fold1(renamedtree_reduce) (#895)GroupingMap::fold_first(renamedreduce) (#902)Itertools::k_smallest(0)to consume the iterator, optimizedItertools::k_smallest(1)(#909)Combinations::nth(#914)MergeBy::fold(#920)CombinationsWithReplacement::nth(#923)FlattenOk::{fold, rfold}(#927)Powerset::nth(#924)assert_equalfor iterators longer thani32::MAX(#932)must_usemessage of non-lazyKMergeByandTupleCombinations(#939)Notable Internal Changes
CONTRIBUTING.md(#767)v0.12.1Compare Source
Added
Itertools::[tuple_]combinations(#822)iterate(#842)CloneandDebugforDiff(#845)DebugforWithPosition(#859)EqforMinMaxResult(#838)From<EitherOrBoth<A, B>>forOption<Either<A, B>>(#843)PeekingNextforRepeatN(#855)Changed
CoalesceBylazy (#801)Filter[Map]Ok::next,Itertools::partition,Unique[By]::next[_back](#818)Itertools::find_position(#837)Positions::next[_back](#816)ZipLongest::fold(#854)Debugbounds forGroupingMapBy(#860)ExactlyOneError::fold(#826)Interleave[Shortest]::fold(#849)MultiPeek::fold(#820)PadUsing::[r]fold(#825)PeekNth::fold(#824)Positions::[r]fold(#813)PutBackN::fold(#823)RepeatN::[r]fold(#821)TakeWhileInclusive::fold(#851)ZipLongest::rfold(#848)Notable Internal Changes
clippyin CI (#740)rustdocin CI (#840)v0.12.0Compare Source
Breaking
take_while_inclusiveconsume iterator by value (#709)Clonebound toUnique(#777)Added
Itertools::try_len(#723)sort_unstable(#796)GroupMap::fold_with(#778, #785)PeekNth::{peek_mut, peek_nth_mut}(#716)PeekNth::{next_if, next_if_eq}(#734)(Option<A>,Option<B>)toEitherOrBoth(#713)Either<A, B>toEitherOrBoth<A, B>(#715)ExactSizeIteratorforTuples(#761)ExactSizeIteratorfor(Circular)TupleWindows(#752)EitherOrBoth<T>a shorthand forEitherOrBoth<T, T>(#719)Changed
#[must_use]annotations on iterator adaptors (#794)Combinationslazy (#795)Intersperse(With)lazy (#797)Permutationslazy (#793)Productlazy (#800)TupleWindowslazy (#602)Combinations::{count, size_hint}(#729)CombinationsWithReplacement::{count, size_hint}(#737)Powerset::fold(#765)Powerset::count(#735)TupleCombinations::{count, size_hint}(#763)TupleCombinations::fold(#775)WhileSome::fold(#780)WithPosition::fold(#772)ZipLongest::fold(#774){min, max}_set*operations requireallocfeature, instead ofstd(#760)tree_fold1(#787)permutations(#724)multiunzip(#770)Notable Internal Changes
Permutations(#739, #748, #790)Merge/MergeBy/MergeJoinByimplementations (#736)Permutations::size_hint(#739)rustfmtin CI (#751)cargo hackto check MSRV (#754)rust-lang-nursery/lazy-static.rs (lazy_static)
v1.5.0Compare Source
rust-lang/regex (regex)
v1.11.1Compare Source
===================
This is a new patch release of
regexthat fixes compilation on nightlyRust when the unstable
patterncrate feature is enabled. Users on nightlyRust without this feature enabled are unaffected.
Bug fixes:
Fix the
Patterntrait implementation as a result of nightly API breakage.v1.11.0Compare Source
===================
This is a new minor release of
regexthat brings in an update to theUnicode Character Database. Specifically, this updates the Unicode data
used by
regexinternally to the version 16 release.New features:
Add new
regex::SetMatches::matched_allmethod.Update to Unicode Character Database (UCD) version 16.
v1.10.6Compare Source
===================
This is a new patch release with a fix for the
unstablecrate feature thatenables
std::str::Patterntrait integration.Bug fixes:
Fix the
Patterntrait implementation as a result of nightly API breakage.v1.10.5Compare Source
===================
This is a new patch release with some minor fixes.
Bug fixes:
Escape invalid UTF-8 when in the
Debugimpl ofregex::bytes::Match.v1.10.4Compare Source
===================
This is a new patch release with some minor fixes.
Fixes a bug with compiling a reverse NFA automaton in
regex-automata.Clarifies that when
Cow::Borrowedis returned from replace APIs, it isequivalent to the input.
v1.10.3Compare 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:
Set
default-features=falsefor thememchrandaho-corasickdependencies.Fix unsound bounds check elision.
v1.10.2Compare Source
===================
This is a new patch release that fixes a search regression where incorrect
matches could be reported.
Bug fixes:
Revert broadening of reverse suffix literal optimization introduced in 1.10.1.
v1.10.1Compare 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:
Loosen ASCII-compatible rules such that regexes like
(?-u:☃)are now allowed.Performance improvements:
Broader the reverse suffix optimization to apply in more cases.
v1.10.0Compare Source
===================
This is a new minor release of
regexthat adds support for start and endword boundary assertions. That is,
\<and\>. The minimum supported Rustversion 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|\Aon the left,\won the right).\>or\b{end}: a Unicode end-of-word boundary (\won the left,\W|\zon the right)).
\b{start-half}: half of a Unicode start-of-word boundary (\W|\Aon theleft).
\b{end-half}: half of a Unicode end-of-word boundary (\W|\zon theright).
The
\<and\>are GNU extensions to POSIX regexes. They have been addedto the
regexcrate because they enjoy somewhat broad support in other regexengines as well (for example, vim). The
\b{start}and\b{end}assertionsare aliases for
\<and\>, respectively.The
\b{start-half}and\b{end-half}assertions are not found in anyother 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:
Add support for
\<and\>word boundary assertions.DFAs now have a
start_statemethod that doesn't use anInput.Performance improvements:
Unicode character class operations have been optimized in
regex-syntax.Make patterns containing lots of literal characters use less memory.
Bug fixes:
Fix a bug that could result in incorrect match spans when using a Unicode word
boundary and searching non-ASCII strings.
Fix panics that can occur in
Ast->Hirtranslation (not reachable fromregexcrate).
Remove guarantees in the API that connect the
uflag with a specific HIRrepresentation.
regex-automatabreaking change release:This release includes a
regex-automata 0.4.0breaking change release, whichwas necessary in order to support the new word boundary assertions. For
example, the
Lookenum has new variants and theLookSettype now usesu32instead of
u16to represent a bitset of look-around assertions. These areoverall very minor changes, and most users of
regex-automatashould be ableto move to
0.4from0.3without any changes at all.regex-syntaxbreaking change release:This release also includes a
regex-syntax 0.8.0breaking change release,which, like
regex-automata, was necessary in order to support the new wordboundary assertions. This release also includes some changes to the
Asttype to reduce heap usage in some cases. If you are using the
Asttypedirectly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7should be able to migrate to0.8without any code changes.regex-literelease:The
regex-lite 0.1.1release contains support for the new word boundaryassertions. There are no breaking changes.
serenity-rs/serenity (serenity)
v0.12.4Compare Source
This is a hotfix release to fix broken behaviour of
Message::author_permissionsbefore it is relied on.Thanks to the following for their contributions:
Deprecations
_invariants.Additions
From<&User>has been added toCreateEmbedAuthor, to avoid consuming the user.Fixes
Message::author_permissionsnow respects permission overrides, as it is documented to.Message::author_permissionsnow respectsSEND_MESSAGES_IN_THREADSwhen used in threads.Documentation improvements
Guild::threadshas been expanded.v0.12.3Compare Source
Thanks to the following for their contributions:
Deprecations
Message(Id)::link_ensuredcan be replaced byMessage(Id)::linkif recieved via event, orMessageId::linkif the message was recieved via a HTTP request.CreateInteractionResponse::PremiumRequiredhas been deprecated and replaced with Premium Buttons.GuildChannel::permissions_for_userhas been deprecated, use the newMessage::author_permissionshelper orGuild::user_permissions_in.Additions
CreateButtonnow implementsFrom<Button>.User::display_namehas been added, as users may have two different names now.CurrentApplicationInfo.GuildMemberFlagshave been added.USE_EXTERNAL_APPSpermission has been added.MessageReferenceKindhas been added to start supporting forwarding.{PartialGuild, Guild}::partial_member_permissionshas been added for more efficent permissions checkingunstable_discord_api.Message::author_permissionshelper has been added, alongsidePermissions::dm_permissions.Deserialisation Fixes
Messages with reactions no longer fail to deserialize due to super reaction changes.
unstable_discord_api-1no longer fail to deserialise.General fixes
GuildId::members_iterdocumentation.CreateAttachmentdocumentation has been updated to be more consistent with other builders.CreateEmbedAuthordocumentation can now spellembedcorrectly.AuthorizingIntegrationOwnersis now usable, as the field was previously private.Partial)Guild::member_permissionsis now usable without cache.ChannelId::delete_messagesdocumentation has been expanded to document the single item case.BulkBanResponsehave been made public.bulk_banendpoint is now usable, previously unusable due toSendissues.v0.12.2Compare 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 checkand 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.Channel::is_nsfwmethod was wrong, useless, and served better byGuildChannel::nsfwMember::highest_role_infois now strictly less powerful than the newGuild::member_highest_roleand can avoid a cache lookup if used correctly.Guild::is_largeis less accurate thanGuild::largeMessage::is_ownis super simple to implement yourselfMessage::is_privatesimply checks ifMessage::guild_idisnone.Event::PresencesReplacedoes not exist, and is a relic from when serenity supported user accounts.TeamMember::permissionsis always["*"], so is useless.Other notable changes
CreateMessage::enforce_nonce, to prevent sending duplicate messages.EditProfile::banner, allowing banners to be set for bots.ChannelId::get_thread_member.Guild::partial_member_permissions_in, which can be used to avoid fetching aMemberin message events just to check permissions.From<User>forCreateEmbedAuthor, setting the author name and icon to theUser's info.UserId::direct_message, so you don't need a fullUserto direct message.Http::default_allowed_mentionsto set theAllowedMentionsto be used with every request.Guild(Id)::bulk_ban, allowing bulk banning without hitting rate limits.v0.12.1Compare 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 thestandard 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
RoleId::to_role_cached- UseGuild::rolesinstead.bitflags!types, resulting in a smaller memory footprint.GuildId/Guildinstead.v0.12.0Compare 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:
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.
This PR was generated by Mend Renovate. View the repository job log.