chore(deps): update all non-major dependencies #52
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:
v3.8
->v3.9
0.20.0
->0.22.0
0.20.0
->0.22.0
0.12
->0.14
0.15
->0.16
1.80.0
->1.82.0
0.2
->0.3
Release Notes
cocogitto/cocogitto-action (cocogitto/cocogitto-action)
v3.9
Compare Source
What's Changed
Full Changelog: cocogitto/cocogitto-action@v3.8...v3.9
lalrpop/lalrpop (lalrpop)
v0.22.0
Compare Source
Breaking changes
lexer
feature no longer implies thestd
feature. Nowlexer
isusable in
no_std
environments. Inno_std
, ParseError only implements theError trait in rust 1.81 or later (since core::error was stablized in 1.81).
Features
alternatives based on cargo features with
not()
,any()
andall()
supportBugfixes
lalrpop_mod!()
now handles imports correctlyv0.21.0
Compare Source
Since the last release, a fair number of the commits have been focused on cleaning
up and improving LALRPOP's documentation. Shout out to Yudai Takada, George
White, and Dinu Blanovschi.
Features
out an error message and exit.
lalrpop::process_src
is now the recommended function to use inbuild.rs
files. Previously the documentation incorrectly suggested that
lalrpop::process_root
looked in./src
instead of.
Bugfixes
exception when trying to handle certain grammars has been resolved.
macro_expansion_limit
.Compatibility note
Adding a limit to the number of times that LALRPOP will attempt to expand a
macro is technically a breaking change. However, the default limit of
200
should be more than enough for the grammars we are currently aware of (which
almost always need a limit of less than 5). This limit is customizable via
Configuration::set_macro_expansion_limit
.If you have a grammar that uses a significant amount of macro expansion steps,
we would be very interested in a PR that adds it to the test suite.
v0.20.2
Compare Source
Special thanks to our newest maintainers, Daniel Burgener and Patrick LaFontaine for helping to coordinate this release.
Features
is-terminal
crate (thanks to Kmeakin!)regex-automata
crate (thanks to QuarticCat!)_
case for token matching can now be set to a higher precedence in match (thanks to fpoli!)Bugfixes
for the report!)
lalrpop's defaults
Compatibility note
1.70
.process_root_unconditionally
now correctly lints as having been deprecated.__
and should not be relied upon are no longer publicly exposed (thanks to arnaudgolfouse!)v0.20.1
Compare Source
Yanked
maciejhirsz/logos (logos)
v0.14.2
: - Optionalforbid_unsafe
feature, fuzzing, book, and more!Compare Source
What's Changed
forbid_unsafe
feature to disable unsafe code by @davidkern in https://github.com/maciejhirsz/logos/pull/413New Contributors
Full Changelog: maciejhirsz/logos@v0.14.1...v0.14.2
v0.14.1
: 0.14.1 - Debug feature and fixesWhat's Changed
Lexer::clone
leak and UB + tests by @Jakobeha in https://github.com/maciejhirsz/logos/pull/390New Contributors
Full Changelog: maciejhirsz/logos@v0.14...v0.14.1
rust-analyzer/rowan (rowan)
v0.16.0
Compare Source
rust-lang/rust (rust)
v1.82.0
Compare Source
==========================
Language
addr_of(_mut)!
macros and the newly stabilized&raw (const|mut)
are now safe to use with all static itemsfor<...>
binder in trait bounds&raw const
and&raw mut
operators (RFC 2582)offset_of!
T
to be live when dropping[T; 0]
const
operands in inline assemblyconst fn
Compiler
aarch64-apple-ios-macabi
andx86_64-apple-ios-macabi
to Tier 2, and ship them with rustup-> !
aarch64-apple-darwin
to Tier 1aarch64-unknown-trusty
andarmv7-unknown-trusty
as tier 3 targetswasm32-wasip2
to Tier 2.Libraries
{Rc,Arc}::make_mut()
toPath
,OsStr
, andCStr
.Stabilized APIs
std::thread::Builder::spawn_unchecked
std::str::CharIndices::offset
std::option::Option::is_none_or
[T]::is_sorted
[T]::is_sorted_by
[T]::is_sorted_by_key
Iterator::is_sorted
Iterator::is_sorted_by
Iterator::is_sorted_by_key
std::future::Ready::into_inner
std::iter::repeat_n
impl<T: Clone> DoubleEndedIterator for Take<Repeat<T>>
impl<T: Clone> ExactSizeIterator for Take<Repeat<T>>
impl<T: Clone> ExactSizeIterator for Take<RepeatWith<T>>
impl Default for std::collections::binary_heap::Iter
impl Default for std::collections::btree_map::RangeMut
impl Default for std::collections::btree_map::ValuesMut
impl Default for std::collections::vec_deque::Iter
impl Default for std::collections::vec_deque::IterMut
Rc<T>::new_uninit
Rc<MaybeUninit<T>>::assume_init
Rc<[T]>::new_uninit_slice
Rc<[MaybeUninit<T>]>::assume_init
Arc<T>::new_uninit
Arc<MaybeUninit<T>>::assume_init
Arc<[T]>::new_uninit_slice
Arc<[MaybeUninit<T>]>::assume_init
Box<T>::new_uninit
Box<MaybeUninit<T>>::assume_init
Box<[T]>::new_uninit_slice
Box<[MaybeUninit<T>]>::assume_init
core::arch::x86_64::_bextri_u64
core::arch::x86_64::_bextri_u32
core::arch::x86::_mm_broadcastsi128_si256
core::arch::x86::_mm256_stream_load_si256
core::arch::x86::_tzcnt_u16
core::arch::x86::_mm_extracti_si64
core::arch::x86::_mm_inserti_si64
core::arch::x86::_mm_storeu_si16
core::arch::x86::_mm_storeu_si32
core::arch::x86::_mm_storeu_si64
core::arch::x86::_mm_loadu_si16
core::arch::x86::_mm_loadu_si32
core::arch::wasm32::u8x16_relaxed_swizzle
core::arch::wasm32::i8x16_relaxed_swizzle
core::arch::wasm32::i32x4_relaxed_trunc_f32x4
core::arch::wasm32::u32x4_relaxed_trunc_f32x4
core::arch::wasm32::i32x4_relaxed_trunc_f64x2_zero
core::arch::wasm32::u32x4_relaxed_trunc_f64x2_zero
core::arch::wasm32::f32x4_relaxed_madd
core::arch::wasm32::f32x4_relaxed_nmadd
core::arch::wasm32::f64x2_relaxed_madd
core::arch::wasm32::f64x2_relaxed_nmadd
core::arch::wasm32::i8x16_relaxed_laneselect
core::arch::wasm32::u8x16_relaxed_laneselect
core::arch::wasm32::i16x8_relaxed_laneselect
core::arch::wasm32::u16x8_relaxed_laneselect
core::arch::wasm32::i32x4_relaxed_laneselect
core::arch::wasm32::u32x4_relaxed_laneselect
core::arch::wasm32::i64x2_relaxed_laneselect
core::arch::wasm32::u64x2_relaxed_laneselect
core::arch::wasm32::f32x4_relaxed_min
core::arch::wasm32::f32x4_relaxed_max
core::arch::wasm32::f64x2_relaxed_min
core::arch::wasm32::f64x2_relaxed_max
core::arch::wasm32::i16x8_relaxed_q15mulr
core::arch::wasm32::u16x8_relaxed_q15mulr
core::arch::wasm32::i16x8_relaxed_dot_i8x16_i7x16
core::arch::wasm32::u16x8_relaxed_dot_i8x16_i7x16
core::arch::wasm32::i32x4_relaxed_dot_i8x16_i7x16_add
core::arch::wasm32::u32x4_relaxed_dot_i8x16_i7x16_add
These APIs are now stable in const contexts:
std::task::Waker::from_raw
std::task::Context::from_waker
std::task::Context::waker
$integer::from_str_radix
std::num::ParseIntError::kind
Cargo
info
cargo subcommandCompatibility Notes
explicit_builtin_cfgs_in_flags
lint in order to prevent incoherent state, eg.windows
cfg active but target is Linux based. The appropriaterustc
flag should be used instead.binary_search
which is significantly improves performance (#128254). However when a sorted slice has multiple values which compare equal, the new implementation may select a different value among the equal ones than the old implementation.MSG_NOSIGNAL
when writing to sockets. This avoids killing the process with SIGPIPE when writing to a closed socket, which matches the existing behavior on other UNIX targets.multivalue
andreference-types
are nowboth enabled by default. These two features both have subtle changes implied
for generated WebAssembly binaries. For the
multivalue
feature, WebAssemblytarget support has changed when upgrading to LLVM 19. Support for generating
functions with multiple returns no longer works and
-Ctarget-feature=+multivalue
has a different meaning than it did in LLVM 18and prior. There is no longer any supported means to generate a module that has
a function with multiple returns in WebAssembly from Rust source code. For the
reference-types
feature the encoding of immediates in thecall_indirect
, acommonly used instruction by the WebAssembly backend, has changed. Validators
and parsers which don't understand the
reference-types
proposal will nolonger accept modules produced by LLVM due to this change in encoding of
immediates. Additionally these features being enabled are encoded in the
target_features
custom section and may affect downstream tooling such aswasm-opt
consuming the module. Generating a WebAssembly module that disablesdefault features requires
-Zbuild-std
support from Cargo and more informationcan be found at
rust-lang/rust#128511.
Internal Changes
These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.
v1.81.0
Compare Source
==========================
Language
extern "C"
functions.&
in elided self lifetimes.#[expect]
for lints (RFC 2383), like#[allow]
with a warning if the lint is not fulfilled.elided_lifetimes_in_associated_constant
to deny.offset_from
: always allow pointers to point to the same address.Compiler
-Cinline-threshold=...
.transmute
size checks.box_pointers
lint.no_std
Xtensa targets:xtensa-esp32-none-elf
,xtensa-esp32s2-none-elf
,xtensa-esp32s3-none-elf
std
Xtensa targets:xtensa-esp32-espidf
,xtensa-esp32s2-espidf
,xtensa-esp32s3-espidf
i686-unknown-redox
arm64ec-pc-windows-msvc
to Tier 2.loongarch64-unknown-linux-musl
to Tier 2 with host tools.wasm32-wasi
. (see compatibility note below)Libraries
PanicInfo
and std'sPanicInfo
. (see compatibility note below){Rc,Arc}::make_mut()
to unsized types.driftsort
and unstableipnsort
. Allslice::sort*
andslice::select_nth*
methods are expected to see significant performance improvements. See the research project for more details.create_dir_all
with respect to empty paths.Stabilized APIs
core::error
hint::assert_unchecked
fs::exists
AtomicBool::fetch_not
Duration::abs_diff
IoSlice::advance
IoSlice::advance_slices
IoSliceMut::advance
IoSliceMut::advance_slices
PanicHookInfo
PanicInfo::message
PanicMessage
These APIs are now stable in const contexts:
char::from_u32_unchecked
(function)char::from_u32_unchecked
(method)CStr::count_bytes
CStr::from_ptr
Cargo
.cargo_vcs_info.json
is always included, even when--allow-dirty
is passed.package.license-file
andpackage.readme
pointing to non-existent files during packaging.--release
/--debug
flag along with the--profile
flag.lib.plugin
key support inCargo.toml
. Rust plugin support has been deprecated for four years and was removed in 1.75.0.Compatibility Notes
Usage of the
wasm32-wasi
target will now issue a compiler warning and request users switch to thewasm32-wasip1
target instead. Both targets are the same,wasm32-wasi
is only being renamed, and this change to the WASI target is being done to enable removingwasm32-wasi
in January 2025.We have renamed
std::panic::PanicInfo
tostd::panic::PanicHookInfo
. The old name will continue to work as an alias, but will result in a deprecation warning starting in Rust 1.82.0.core::panic::PanicInfo
will remain unchanged, however, as this is now a different type.The reason is that these types have different roles:
std::panic::PanicHookInfo
is the argument to the panic hook in std context (where panics can have an arbitrary payload), whilecore::panic::PanicInfo
is the argument to the#[panic_handler]
in no_std context (where panics always carry a formatted message). Separating these types allows us to add more useful methods to these types, such asstd::panic::PanicHookInfo::payload_as_str()
andcore::panic::PanicInfo::message()
.The new sort implementations may panic if a type's implementation of
Ord
(or the given comparison function) does not implement a total order as the trait requires.Ord
's supertraits (PartialOrd
,Eq
, andPartialEq
) must also be consistent. The previous implementations would not "notice" any problem, but the new implementations have a good chance of detecting inconsistencies, throwing a panic rather than returning knowingly unsorted data.In very rare cases, a change in the internal evaluation order of the trait
solver may result in new fatal overflow errors.
Internal Changes
These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.
auto
CI job to check kernel builds.v1.80.1
Compare Source
===========================
dead_code
lint from 1.80.0rust-analyzer/smol_str (smol_str)
v0.3.2
Compare Source
SmolStrBuilder::push
incorrectly padding null bytes when spilling onto the heap on amultibyte character push
v0.3.1
Compare Source
SmolStrBuilder
leaking implementation detailsv0.3.0
Compare Source
SmolStr::new_inline_from_ascii
functionSmolStr::to_string
in favor ofToString::to_string
impl AsRef<[u8]> for SmolStr
implimpl AsRef<OsStr> for SmolStr
implimpl AsRef<Path> for SmolStr
implSmolStrBuilder
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.