chore(deps): lock file maintenance rust crates #11973
Merged
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:
=3.17.0
->=3.19.0
0.15.11
->0.16.0
3.0.0
->3.0.1
2.9.0
->2.10.0
2.3.0
->2.3.1
11.2.0
->11.3.0
0.2.1
->0.2.3
🔧 This Pull Request updates lock files to use the latest dependency versions.
Release Notes
fitzgen/bumpalo (bumpalo)
v3.19.0
Released 2025-06-24.
Added
bumpalo::collections::Vec::retain_mut
, similar tostd::vec::Vec::retain_mut
.v3.18.1
Compare Source
Released 2025-06-05.
Removed
allocator-api2
version bump from 3.18.0, as it was not actuallysemver compatible.
v3.18.0
Compare Source
Released 2025-06-05.
Added
Bump
arena, which can provide speed ups when allocating objects whosealignment is less than or equal to that minimum.
serde
serialization support forbumpalo::collections::String
.Changed
extend_from_slice
implementation with a formally-verified versionthat is also faster and more-optimizable for LLVM.
allocator-api2
support to version0.3.*
.Fixed
allocated_bytes
metrics helper was accidentallyincluding the size of
bumpalo
's footer, rather than just reporting theuser-allocated bytes.
console-rs/console (console)
v0.16.0
Compare Source
What's Changed
The 0.15.12 release was yanked after it turned out to be semver-incompatible with existing usage by several of the most popular dependent crates, because it introduced a
std
feature -- and those crates useddefault-features = false
but relied on thestd
-guarded features.The 0.16.0 API should be semver-compatible with the 0.15.x API except for the need for the
std
feature.Refer to the 0.15.12 release notes for more information.
v0.15.12
Compare Source
What's Changed
Boshen/criterion2.rs (criterion2)
v3.0.1
Compare Source
Other
indexmap-rs/indexmap (indexmap)
v2.10.0
Compare Source
extract_if
methods toIndexMap
andIndexSet
, similar to themethods for
HashMap
andHashSet
with ranges likeVec::extract_if
.#[track_caller]
annotations to functions that may panic.oxc-project/oxc-miette (miette)
v2.3.1
Compare Source
Chore
oxc-project/oxc-resolver (oxc_resolver)
v11.3.0
Compare Source
🚀 Features
exports
field inrequire('../directory')
(#572) (by @Boshen)ResolveResult::builtin
information (#575) (by @Boshen)📚 Documentation
allowPackageExportsInDirectoryResolve
(by @Boshen)Contributors
v11.2.1
Compare Source
🐛 Bug Fixes
pnp_manifest
is included withyarn_pnp
feature (#555)💼 Other
debug = false
in[profile.dev]
and[profile.test]
(#554)📚 Documentation
alias
andfallback
options type and description (#557)ibraheemdev/papaya (papaya)
v0.2.3
: 0.2.3Compare Source
v0.2.2
: 0.2.2Compare Source
HashMap
with key/value types that are aligned to less than 8 bytes. This is likely only relevant on 32-bit platforms (https://github.com/ibraheemdev/papaya/pull/74).Configuration
📅 Schedule: Branch creation - "before 9am on monday" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.