-
-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
chore(deps): update all non-major dependencies (minor) #189
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch
base: main
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
fix(deps): update rust crate tokio to 1.32.0
chore(deps): update all non-major dependencies
Sep 8, 2023
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
September 8, 2023 17:15
76724c2
to
2e9b45c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
October 9, 2023 22:33
918d81c
to
ed2c246
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 24, 2023 20:41
ed2c246
to
720fd21
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
November 14, 2023 21:45
0d47ec9
to
2d86f7e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 19, 2023 02:59
2d86f7e
to
b242f6e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 27, 2023 20:33
b242f6e
to
41dc10f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
December 9, 2023 01:27
41dc10f
to
163a34a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
December 19, 2023 19:23
163a34a
to
fa1680b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
January 11, 2024 17:26
fa1680b
to
758408a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
January 29, 2024 21:56
36f480a
to
0318818
Compare
renovate
bot
changed the title
chore(deps): update all non-major dependencies
fix(deps): update all non-major dependencies (minor)
Jan 29, 2024
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
February 2, 2024 13:37
f5b1bca
to
8da4510
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 19, 2024 08:13
8da4510
to
c339d94
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 8, 2024 11:01
c339d94
to
d2f5dd3
Compare
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
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
March 14, 2024 10:45
4388311
to
626cbd3
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
March 28, 2024 20:33
467df6c
to
76c15a4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
May 16, 2024 19:28
76c15a4
to
2084133
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
May 28, 2024 10:23
2084133
to
55c6e4d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
June 22, 2024 00:26
419051b
to
574877a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
July 17, 2024 11:40
f30abda
to
4a3e66d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
July 27, 2024 11:20
6e85c14
to
0751708
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
August 7, 2024 22:42
518cae1
to
ea58dfb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
August 17, 2024 19:06
e6100bb
to
52bda1f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
August 30, 2024 09:12
eedf5d9
to
d37a0d5
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 16, 2024 11:57
d37a0d5
to
38cfc02
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
September 30, 2024 13:21
21a80a1
to
a566106
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
October 8, 2024 19:55
7db87ee
to
d9355a8
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
October 24, 2024 15:46
0ee99ce
to
06c20fb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 30, 2024 08:00
06c20fb
to
c857bd6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 7, 2024 14:25
c857bd6
to
dfa775a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 13, 2024 01:24
dfa775a
to
3e2be3a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
v4.0.0
->v4.1.2
v6.3.0
->v6.9.0
v3.0.0
->v3.3.0
0.11.0
->0.13.0
1.4.0
->1.5.0
1.9.6
->1.11.1
0.11.6
->0.12.0
1.31.0
->1.41.1
Release Notes
actions/cache (actions/cache)
v4.1.2
Compare Source
What's Changed
isGhes
logic by @jww3 in https://github.com/actions/cache/pull/14744.1.2
release by @Link- in https://github.com/actions/cache/pull/1477New Contributors
Full Changelog: actions/cache@v4...v4.1.2
v4.1.1
Compare Source
What's Changed
cache-hit
output by @joshmgross in https://github.com/actions/cache/pull/1467Full Changelog: actions/cache@v4.1.0...v4.1.1
v4.1.0
Compare Source
What's Changed
save-always
input by @joshmgross in https://github.com/actions/cache/pull/1452New 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
repository
andghtoken
attributes 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.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
DoubleEndedIterator
forConsTuples
(#853)MultiProduct
fused and fixed on an empty iterator (#835, #834)iproduct!
to return tuples for maxi one iterator too (#870)PutBack::put_back
to 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)DoubleEndedIterator
forProcessResults
(#910)Debug
forFormatWith
(#931)Itertools::get
(#891)Changed
Itertools::group_by
(renamedchunk_by
) (#866, #879)unfold
(usestd::iter::from_fn
instead) (#871)GroupingMapBy
(#873, #876)Fn
bounds toFnMut
indiff_with, Itertools::into_group_map_by
(#886)Debug/Clone
bounds forMapInto
(#889)use_alloc
feature (#887)Itertools::set_from
(#888)README.md
(#890)Cargo.toml
(#894)Itertools::k_smallest
on 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_equal
for iterators longer thani32::MAX
(#932)must_use
message of non-lazyKMergeBy
andTupleCombinations
(#939)Notable Internal Changes
CONTRIBUTING.md
(#767)v0.12.1
Compare Source
Added
Itertools::[tuple_]combinations
(#822)iterate
(#842)Clone
andDebug
forDiff
(#845)Debug
forWithPosition
(#859)Eq
forMinMaxResult
(#838)From<EitherOrBoth<A, B>>
forOption<Either<A, B>>
(#843)PeekingNext
forRepeatN
(#855)Changed
CoalesceBy
lazy (#801)Filter[Map]Ok::next
,Itertools::partition
,Unique[By]::next[_back]
(#818)Itertools::find_position
(#837)Positions::next[_back]
(#816)ZipLongest::fold
(#854)Debug
bounds 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
clippy
in CI (#740)rustdoc
in CI (#840)v0.12.0
Compare Source
Breaking
take_while_inclusive
consume iterator by value (#709)Clone
bound 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)ExactSizeIterator
forTuples
(#761)ExactSizeIterator
for(Circular)TupleWindows
(#752)EitherOrBoth<T>
a shorthand forEitherOrBoth<T, T>
(#719)Changed
#[must_use]
annotations on iterator adaptors (#794)Combinations
lazy (#795)Intersperse(With)
lazy (#797)Permutations
lazy (#793)Product
lazy (#800)TupleWindows
lazy (#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 requirealloc
feature, instead ofstd
(#760)tree_fold1
(#787)permutations
(#724)multiunzip
(#770)Notable Internal Changes
Permutations
(#739, #748, #790)Merge
/MergeBy
/MergeJoinBy
implementations (#736)Permutations::size_hint
(#739)rustfmt
in CI (#751)cargo hack
to check MSRV (#754)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 nightlyRust when the unstable
pattern
crate feature is enabled. Users on nightlyRust without this feature enabled are unaffected.
Bug fixes:
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 theUnicode Character Database. Specifically, this updates the Unicode data
used by
regex
internally to the version 16 release.New features:
Add new
regex::SetMatches::matched_all
method.Update to Unicode Character Database (UCD) version 16.
v1.10.6
Compare Source
===================
This is a new patch release with a fix for the
unstable
crate feature thatenables
std::str::Pattern
trait integration.Bug fixes:
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:
Escape invalid UTF-8 when in the
Debug
impl ofregex::bytes::Match
.v1.10.4
Compare 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::Borrowed
is returned from replace APIs, it isequivalent 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:
Set
default-features=false
for thememchr
andaho-corasick
dependencies.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:
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:
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.0
Compare Source
===================
This is a new minor release of
regex
that 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|\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 theleft).
\b{end-half}
: half of a Unicode end-of-word boundary (\W|\z
on theright).
The
\<
and\>
are GNU extensions to POSIX regexes. They have been addedto the
regex
crate 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_state
method 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->Hir
translation (not reachable fromregex
crate).
Remove guarantees in the API that connect the
u
flag with a specific HIRrepresentation.
regex-automata
breaking change release:This release includes a
regex-automata 0.4.0
breaking change release, whichwas necessary in order to support the new word boundary assertions. For
example, the
Look
enum has new variants and theLookSet
type now usesu32
instead of
u16
to represent a bitset of look-around assertions. These areoverall very minor changes, and most users of
regex-automata
should be ableto move to
0.4
from0.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 wordboundary assertions. This release also includes some changes to the
Ast
type to reduce heap usage in some cases. If you are using the
Ast
typedirectly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7
should be able to migrate to0.8
without any code changes.regex-lite
release:The
regex-lite 0.1.1
release contains support for the new word boundaryassertions. There are no breaking changes.
serenity-rs/serenity (serenity)
v0.12.4
Compare Source
This is a hotfix release to fix broken behaviour of
Message::author_permissions
before it is relied on.Thanks to the following for their contributions:
Deprecations
_in
variants.Additions
From<&User>
has been added toCreateEmbedAuthor
, to avoid consuming the user.Fixes
Message::author_permissions
now respects permission overrides, as it is documented to.Message::author_permissions
now respectsSEND_MESSAGES_IN_THREADS
when used in threads.Documentation improvements
Guild::threads
has been expanded.v0.12.3
Compare Source
Thanks to the following for their contributions:
Deprecations
Message(Id)::link_ensured
can be replaced byMessage(Id)::link
if recieved via event, orMessageId::link
if the message was recieved via a HTTP request.CreateInteractionResponse::PremiumRequired
has been deprecated and replaced with Premium Buttons.GuildChannel::permissions_for_user
has been deprecated, use the newMessage::author_permissions
helper orGuild::user_permissions_in
.Additions
CreateButton
now implementsFrom<Button>
.User::display_name
has been added, as users may have two different names now.CurrentApplicationInfo
.GuildMemberFlags
have been added.USE_EXTERNAL_APPS
permission has been added.MessageReferenceKind
has been added to start supporting forwarding.{PartialGuild, Guild}::partial_member_permissions
has been added for more efficent permissions checkingunstable_discord_api
.Message::author_permissions
helper has been added, alongsidePermissions::dm_permissions
.Deserialisation Fixes
Messages with reactions no longer fail to deserialize due to super reaction changes.
unstable_discord_api
-1
no longer fail to deserialise.General fixes
GuildId::members_iter
documentation.CreateAttachment
documentation has been updated to be more consistent with other builders.CreateEmbedAuthor
documentation can now spellembed
correctly.AuthorizingIntegrationOwners
is now usable, as the field was previously private.Partial
)Guild::member_permissions
is now usable without cache.ChannelId::delete_messages
documentation has been expanded to document the single item case.BulkBanResponse
have been made public.bulk_ban
endpoint is now usable, previously unusable due toSend
issues.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.Channel::is_nsfw
method was wrong, useless, and served better byGuildChannel::nsfw
Member::highest_role_info
is now strictly less powerful than the newGuild::member_highest_role
and can avoid a cache lookup if used correctly.Guild::is_large
is less accurate thanGuild::large
Message::is_own
is super simple to implement yourselfMessage::is_private
simply checks ifMessage::guild_id
isnone
.Event::PresencesReplace
does not exist, and is a relic from when serenity supported user accounts.TeamMember::permissions
is 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 aMember
in 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 fullUser
to direct message.Http::default_allowed_mentions
to set theAllowedMentions
to be used with every request.Guild
(Id
)::bulk_ban
, allowing bulk banning without hitting rate limits.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 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::roles
instead.bitflags!
types, resulting in a smaller memory footprint.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:
Now, users instead write the following code:
Or, inline like so:
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 takemut self
and returnSelf
, 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 apub HashMap<&'static str, T>
; the hashmap has been flattened into concrete private fields.Some benefits to this new approach to builders are:
Attachments
AttachmentType
enum has been replaced with aCreateAttachment
builder struct. This struct has thefile
,path
, andurl
constructors that eagerly evaluate the data passed to them -CreateAttachment
simply stores the resulting raw data. This is in contrast toAttachmentType
which lazily carried filepaths/urls with it, and haddata
andfilename
methods for resolving them. Additionally, theCreateAttachment::to_base64
method can be used to manually encode an attachment if needed.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.