Repository navigation
fix(deps): update rust-minor - #185
Open
renovate[bot] wants to merge 2 commits into
Open
renovate[bot] wants to merge 2 commits into
renovate[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
renovate
Bot
force-pushed
the
renovate/rust-minor
branch
29 times, most recently
from
September 23, 2026 00:47
8aa08a2 to
9e8971c
Compare
renovate
Bot
force-pushed
the
renovate/rust-minor
branch
9 times, most recently
from
September 28, 2026 19:49
56b0cab to
f86988e
Compare
renovate
Bot
force-pushed
the
renovate/rust-minor
branch
3 times, most recently
from
October 3, 2026 17:33
eb5abe7 to
3ce82a4
Compare
renovate
Bot
force-pushed
the
renovate/rust-minor
branch
9 times, most recently
from
October 20, 2026 19:13
86bf8ea to
4033f54
Compare
renovate
Bot
force-pushed
the
renovate/rust-minor
branch
6 times, most recently
from
October 28, 2026 18:57
4cf7d1f to
9d55926
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Three of the 0.x "minor" updates in this group are breaking, because each crate has to match another crate's version: - getrandom stays at 0.2 in morphir-gleam-binding. The dependency only turns on the `custom` feature of the 0.2 copy that gleam-core's dependencies use on wasm32-unknown-unknown; 0.4 has no such feature and would add an unrelated copy. - ecow stays at =0.2.6, the version gleam-core uses, because morphir-gleam-binding passes EcoString values to and from gleam-core. - untrusted stays at 0.7.1 in morphir-package-tough, because aws-lc-rs 1.18 takes an untrusted 0.7 Reader. rusqlite 0.41 returns an iterator from Statement::column_names, so drop the redundant into_iter() that clippy now rejects. The lock file is resolved again; Renovate's update had failed on getrandom and left the old versions in place. Verified with cargo clippy --all-targets --all-features -D warnings, mise run test:unit (1209 passed) and cargo test --workspace --all-features --tests (4014 passed). Beads: morphir-x4ep.3 Claude-Session: https://claude.ai/code/session_016vWNpLC7n2Fat4wgyZR75p
This branch has not been deployed
This file contains hidden or 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
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
1.1.1→1.2.01.18.1→1.19.00.22→0.230.22.1→0.23.01.4.7→1.10.0=0.2.6→=0.3.11.30.0→1.41.00.2→0.41.0.1→1.2.0=1.0.1→=1.2.00.56→0.600.56→0.600.27→0.28=0.40.2→=0.41.1=0.40.2→=0.41.10.40→0.410.8→0.91.53.1→1.54.11.53.1→1.54.10.9→0.130.7.1→0.9.01.26.1→1.29.00.259→0.2621.259.0→1.262.00.62.0→0.63.0Release Notes
dcchut/async-recursion (async-recursion)
v1.2.0Compare Source
What's Changed
Full Changelog: dcchut/async-recursion@v1.1.1...v1.2.0
aws/aws-lc-rs (aws-lc-rs)
v1.19.0: aws-lc-rs v1.19.0Compare Source
What's Changed
OperatingMode::OFB,OperatingMode::CFB8, andOperatingMode::CFB1for AES-128, AES-192, and AES-256 through both the one-shot and streaming cipher APIs.aws_lc_rs::try_fips_self_test(), allowing applications to re-run all AWS-LC cryptographic algorithm self-tests without calling the sys crate through unsafe FFI. This does not re-run the module integrity test.aws_lc_rs::unstable::digest::KECCAK256andKECCAK256_OUTPUT_LENbehind theunstablefeature for use with the existingdigest::digestanddigest::ContextAPIs.RsaPssSaltLength::{Digest, Max, Custom}andwith_pss_salt_lengthbuilders onRsaSignatureEncodingandRsaParameters, covering signing and verification for both message and precomputed-digest APIs.Clonefor signing key pairs by @JakeHuneau in #1277rsa::KeyPair,EcdsaKeyPair,Ed25519KeyPair, andPqdsaKeyPaircan now be cloned directly rather than wrapped in anArc.EVP_PKEY; key material is not duplicated, and a clone remains usable after the original is dropped.Upstream AWS-LC
aws-lc-sysv0.47.0 aligns with AWS-LC v5.12.0 (previously v5.11.0).aws-lc-fips-sysv0.14.4 updates its bundled AWS-LC FIPS 4.2.0 snapshot with recent FIPS 4.x backports.Build Improvements
aws-lc-syssystem-library path now accepts AWS-LC 4.2.0 or newer, previously 5.7.0, allowing use of a FIPS 4.x system library.unstablefeature requires AWS-LC 5.7.0 or newer because unstable APIs currently include Keccak-256. Bundled-source builds are unaffected.cccompiler detection across builds by @johncarmack1984 in #1273Issues Being Closed
Cloneforrsa::KeyPair-- #1260Other Merged PRs
New Contributors
Full Changelog: aws/aws-lc-rs@v1.18.2...v1.19.0
v1.18.2: aws-lc-rs v1.18.2Compare Source
What's Changed
EqandPartialEqfor RSA and EdDSA parameters by @dsykes16 in #1228RsaParameterscan now be compared directly against RSA verification constants. Algorithms with different digests, padding schemes, or modulus-size ranges compare unequal.EdDSAParametersalso gains equality support.wasm32-wasip2andwasm32-wasip3support by @ricochet in #1239aws-lc-sysconsumers must disable the defaultall-bindingsfeature for these targets.RandomizedNonceKey::open_in_placedocumentation by @Serophots in #1227Upstream AWS-LC
aws-lc-sysv0.46.0 aligns with AWS-LC v5.11.0 (previously v5.7.0). See also the release notes for v5.8.0, v5.9.0, and v5.10.0.Ed25519C-implementation decoder now rejects non-canonical public keys, matching the assembly-optimized implementations: aws/aws-lc#3457aws-lc-fips-sysv0.14.3 updates its bundled AWS-LC FIPS 4.2.0 snapshot and regenerates bindings. It remains on the FIPS 4.x release line.Build Improvements
FIPS_modereferences with GNU ld.bfd when linking a prebuilt static FIPS library, including binaries that do not call crypto and builds where LTO removes those calls.staticliboutputs. This can increase binary size; dynamic FIPS and non-FIPS linking are unchanged.RUSTFLAGS. TheAWS_LC_SYS_NO_U1_BINDINGSworkaround is no longer needed.CFLAGSand newerccversions by @justsmth in #1254-O2to override its required-O0.AWS_LC_SYS_CCin the main library build by @justsmth in #1255cccaches environment reads.Issues Being Closed
codegen-backend = "cranelift"-- #1231FIPS_modewhen linking a prebuilt FIPS module into a binary that does not use crypto -- #1246Other Merged PRs
New Contributors
Full Changelog: aws/aws-lc-rs@v1.18.1...v1.18.2
marshallpierce/rust-base64 (base64)
v0.23.1Compare Source
v0.23.0Compare Source
simd-unsafefeature:Simdpicks the bestinstruction set at runtime (AVX2 on
x86_64, NEON onaarch64) and falls back to the scalarGeneralPurposeengine, whileAvx2andNeontarget one instruction set with no runtimedetection and work in
no_std. The engines support the standard and URL-safe alphabets.rust-lang/cc-rs (cc)
v1.10.0Compare Source
Added
Fixed
Other
v1.9.0Compare Source
Added
compile_commands.json(#1990)Fixed
RUSTC_WRAPPERto thecl.execc finds itself (#2022)Other
v1.8.0Compare Source
Added
CC_PREFER_CLANG_CL_OVER_MSVCto overrideprefer_clang_cl_over_msvc(#2001)Fixed
Other
NVCCand other environment variables (#2005)v1.7.0Compare Source
Added
Tool::get_envs, deprecate Tool::env and store tool env asArc<OsStr>pairs (#1985)c++when Clang uses libc++ (#1978)CC_MASM_ASMand fall back tollvm-mlfor MASM files (#1975)Fixed
Other
v1.6.0Compare Source
Added
Build::create_archiveandemit_link_directives(#1972)Build, on first use (#1969)Build::message_loggerfor structured access to cc's messages (#1967)CXXSTDLIB_STATICto link the C++ stdlib statically from outside (#1957)Fixed
parallel(#1959)Other
parallel(#1973)armeb-unknown-linux-gnueabi(#1958)v1.5.1Compare Source
Fixed
-bundle, once perBuild(#1955)Other
v1.5.0Compare Source
Added
Fixed
/linkflags with a warning (#1949)windows_sysmore private and re-export types needed by cc-rs (#1944)Other
Fixed
-Tpimmediately before.ccsources on MSVC (not clang-cl) when compiling C++ so they are not treated as object files (#1877)typst/ecow (ecow)
v0.3.1: Version 0.3.1Compare Source
EcoBytestype, similar toEcoStringbut without enforcement of UTF-8 (thanks to @flyingmutant and @imbrem)EcoString::{capacity, reserve}no_std(thanks to @pedrodesu)v0.3.0: Version 0.3.0Compare Source
EcoString::{insert, insert_str, remove}methodsEcoVec::{drain, splice}methodsToEcoStringtrait for conveniently converting something that implementsDisplayto anEcoStringAsRef<[u8]>,AsRef<OsStr>, andAsRef<Path>impls forEcoString(thanks to @tingerrr)FromIterator<&str>andExtend<&str>impls forEcoString(thanks to @pedrodesu)EcoVec::reservein the case it is non-unique (thanks to @ndren)#[clippy::format_args]toeco_formatmacro so thateco_format!calls are linted by clippy (thanks to @isuffix)This is a re-release of v0.2.7 which has been yanked. See #63 for more information.
v0.2.7: Version 0.2.7Compare Source
This release has been yanked, use v0.3.0 instead. See #63 for more information.
extism/extism (extism)
v1.41.0Compare Source
What's Changed
Full Changelog: extism/extism@v1.40.0...v1.41.0
rust-random/getrandom (getrandom)
v0.4.3Compare Source
Added
wasm64-unknown-unknowntarget support forwasm_jsbackend #848Changed
wasip2andwasip3dependencies in favor of manual bindings #830v0.4.2Compare Source
Changed
r-efidependency to v6 #814Fixed
errnoonly when it is set #810ProcessPrngon Windows #811v0.4.1Compare Source
Fixed
v0.4.0Compare Source
Added
RawOsErrortype alias #739SysRngbehind new featuresys_rng#751extern_implopt-in backend #786 #794Changed
v0.3.4Compare Source
Major change to
wasm_jsbackendNow, when the
wasm_jsfeature is enabled, thewasm_jsbackend will be usedby default. Users of
wasm32-unknown-unknowntargeting JavaScript environmentslike the Web and Node.js will no longer need to specify:
in
RUSTFLAGSfor the crate to compile. They can now simple enable a feature.Note: this should not affect non-JS users of the
wasm32-unknown-unknowntarget. Using
--cfg getrandom_backendwill still override the source ofrandomness even if the
wasm_jsfeature is enabled. This includes--cfg getrandom_backend=customand--cfg getrandom_backend=unsupported.For more information, see the discussions in #671, #675, and #730.
Added
unsupportedopt-in backend #667windows_legacyopt-in backend #724Changed
linux_rawopt-in backend on ARM targets #688getrandomsyscall on all RISC-V Linux targets #699wasidependency withwasip2#721wasm_jsbackend by default if thewasm_jsfeature is enabled #730Removed
rustc-dep-of-stdcrate feature #694v0.3.3Compare Source
Changed
compile_error!s #639Fixed
v0.3.2Compare Source
Added
efi_rngopt-in backend #570linux_rawopt-in backend #572.cargo/config.tomlexample in the crate-level docs #591getrandom_test_linux_without_fallbackconfiguration flag to test that file fallbackis not triggered in the
linux_android_with_fallbackbackend #605*-linux-nonetargets #618Changed
wasidependency to v0.14 #594#[inline]attribute to the inner functions #596dlsymon MUSL targets in thelinux_android_with_fallbackbackend #602linux_android.rsand usegetrandom.rsinstead #603RtlGenRandomon Windows targets when compiling with pre-1.78 Rust #610Errortype #614windows-targetsdependency and useraw-dylibdirectly #627Removed
Error::INTERNAL_STARTandError::CUSTOM_STARTassociated constants #614v0.3.1Compare Source
Fixed
v0.3.0Compare Source
Breaking Changes
Changed
getrandomandgetrandom_uninitfunctions tofillandfill_uninitrespectively #532Removed
wasm32-wasitarget support (usewasm32-wasip1orwasm32-wasip2instead) #499linux_disable_fallback,rdrand,js,test-in-browser, andcustomcrate featuresin favor of configuration flags #504
register_custom_getrandom!macro #504From<NonZeroU32>forErrorandError::codemethod #507Errorconstants #562Changed
ProcessPrngon Windows 10 and up, and useRtlGenRandomon older Windows versions #415strerror_rfor retrieving error code descriptions #440usizeis the native word size in therdrandbackend #442errnowhenlibcdid not indicate error on Solaris #448libpthread's mutex tofutexon Linux and tonanosleep-based wait loopon other targets in the
use_filebackend #490EAGAINwhile polling/dev/randomon Linux #522wasm_jsbackend(bumps minimum supported Node.js version to v19) #557
js_namespacein thewasm_jsbackend #559Added
wasm32-wasip1andwasm32-wasip2support #499getrandom_backendconfiguration flag for selection of opt-in backends #504Error::new_custommethod #507rndropt-in backend #512u32andu64functions for generating random values of the respective type #544wasm32v1-nonesupport in thewasm_jsbackend #560wasm_jscrate feature which allows users to enable thewasm_jsopt-in backend #574Fixed
KERN_ARND#555amazon-ion/ion-rust (ion-rs)
v1.2.0Compare Source
Summary
This release makes binary writes 22–50% faster in benchmarks: writer symbol tables no longer allocate per symbol, and readers no longer build a text→SID map (#1065). For custom
WriteAsIonimplementations,IonError::applicationmakes it possible to raise application-specific errors (#1073), and the experimentalValueWriter::Encodingmakes it possible to encode a nested stream, such as a blob payload, in the same encoding as the enclosing writer (#1079).WriteConfig::with_max_depthsets a limit on how deeply containers can nest when writing; the default is 65,535 (#1074). Finally,experimental-serdecan now deserialize internally tagged enums (#[serde(tag = "...")]) from both text and binary Ion (#1077).What's Changed
AGENTS.mdwith contributor guidance for coding agents by @popematt in #1070StructWriter::writevalue is written by @popematt in #1072WriteConfig::with_max_depthby @popematt in #1074Rc::assume_initinIoBuffer::alloc_zeroedby @popematt in #1075IonError::Applicationfor user-raised errors by @popematt in #1073ValueWriter::Encodingby @popematt in #1079unsafefromExpandingReaderby @popematt in #1078LazyElementsound without lifetime erasure by @popematt in #1080DecimalandTimestampas byte payloads by @popematt in #1082New Contributors
Full Changelog: amazon-ion/ion-rust@v1.1.0...v1.2.0
v1.1.0Compare Source
What's Changed
This release has smaller and faster in-memory representations for
Timestamp,Decimal,Int,UInt,IonError, andElementannotations, plus faster text parsing and binary encoding. It also removes the incomplete Ion 1.1 implementation.New Features
TimestampBuilder::localize_to_offset(#1055)is_inlineonInt,UInt,Coefficient, andDecimal(#1068)Performance
Timestampis now a 16-byte packed representation (#1041)Decimalis now 24 bytes, backed by an overflowing-integerCoefficient(#1044, #1057)IntandUIntare backed by the same overflowing-integer representation (#1064)IonErroris 32 bytes; large payloads are boxed (#1043)Elementannotations are packed into a single tagged pointer (#1053)Structfields are stored in a boxed slice with a lazily built index (#1048)VarUInt/VarIntwriters and stack-encoded int/decimal magnitudes (#1047, #1049)Breaking change to experimental features
experimental-ion-1-1Cargo feature and the incomplete Ion 1.1 implementation behind it have been removed (#1056). Crates that enableexperimental-ion-1-1must remove it from their feature list to build with this release.Other changes
chronodependency is now only pulled in by theexperimental-chronofeature.New Contributors
Full Changelog: amazon-ion/ion-rust@v1.0.1...v1.1.0
Stranger6667/jsonschema (jsonschema)
v0.60.2Fixed
unevaluated*schemas with$refcycles across$idresources.v0.60.1Fixed
f64inconst,enum,minimum,maximum,exclusiveMinimum,exclusiveMaximumandtype: integerwhen another crate in the build enablesserde_json/arbitrary_precisionwhile thearbitrary-precisionfeature is off. #1790#[jsonschema::validator]panicking during expansion, or generating code that panics, on schema numbers pastf64when another crate in the build enablesserde_json/arbitrary_precisionwhile thearbitrary-precisionfeature is off. Such numbers are compile errors, as without thatserde_jsonfeature. #1790const,enumanduniqueItemstreating objects with the same members in a different key order as unequal when another crate in the build enablesserde_json/preserve_order. #1791type: integer,const,enum,uniqueItems,multipleOf,minimum,maximum,exclusiveMinimumandexclusiveMaximumfor numbers with exponents past one million, such as1e-2000000, with thearbitrary-precisionfeature.#[jsonschema::validator]rejectingmultipleOfwith a positive divisor below the smallestf64, such as1e-400, with thearbitrary-precisionfeature.Performance
const,enum,uniqueItems,type: integer,multipleOf,minimum,maximum,exclusiveMinimumandexclusiveMaximumwith thearbitrary-precisionfeature taking time growing faster than the square of the digit count, instead of at most the square.arbitrary-precisionfeature taking time linear in their written length instead of quadratic in their digit count.v0.60.0Changed
ValidationErrorKind::EnumandValidationErrorKind::Constantholding their values asArc<Value>shared with the validator, instead of a copy per error. #1777Performance
itemsandadditionalPropertieslooking up a single-keyword subschema once per array or object instead of once per value.is_validandvalidatereading fewer cache lines per subschema, by keeping error locations apart from validators.is_validon recursive schemas caching only$refresults that took many steps to compute, instead of every one.$refnesting depth, not quadratic. #1778v0.59.0Added
-as a path reads the schema or an instance from stdin.-Vas the version flag;-vstays as an alias.Changed
3for errors that prevent a verdict and2for usage errors, so1always means an invalid instance or schema.Configuration
📅 Schedule: (UTC)
🚦 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.