Repository navigation
fix(deps): update rust-major (major) - #293
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
renovate
Bot
force-pushed
the
renovate/major-rust-major
branch
from
October 9, 2026 08:25
1412781 to
69506cf
Compare
renovate
Bot
force-pushed
the
renovate/major-rust-major
branch
5 times, most recently
from
October 16, 2026 12:27
011bcb3 to
ebb1c0a
Compare
renovate
Bot
force-pushed
the
renovate/major-rust-major
branch
3 times, most recently
from
October 24, 2026 18:45
49405cc to
fd55db0
Compare
renovate
Bot
force-pushed
the
renovate/major-rust-major
branch
3 times, most recently
from
October 28, 2026 00:25
f40d473 to
c27ef51
Compare
DamianReeves
force-pushed
the
renovate/major-rust-major
branch
from
October 29, 2026 08:06
c27ef51 to
dec6c9c
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. |
granit-parser 2.0 and serde-saphyr 2.0 put comment support behind a default `comments` feature. The workspace builds both without default features and never kept comments, so: - the YAML profile reader drops its Event::Comment arm: without the feature the parser skips and validates comments and emits no event; - morphir-config drops serde-saphyr's emit_comments option, which no longer exists without the feature, and replaces the deprecated reject_non_finite_typeless_float with non_finite_float_policy: NonFiniteFloatPolicy::Reject, the same behavior. granit-parser's own emit_comments option is unchanged. zip 9 returns ZipResult<Cow<str>> from ZipFile::name(), because a name can fail to decode. The tool archive reader now refuses such an entry as an invalid ZIP entry, like the other entry errors it reports. ed25519-zebra 5 needed no changes. Verified with cargo clippy --all-targets --all-features -D warnings, cargo test --workspace --all-features (4012 passed) and the vendored tough crate's locked tests (98 passed, plus experimental_storage). Beads: morphir-x4ep.4 Claude-Session: https://claude.ai/code/session_016vWNpLC7n2Fat4wgyZR75p
DamianReeves
force-pushed
the
renovate/major-rust-major
branch
from
November 1, 2026 02:04
dec6c9c to
ba345f9
Compare
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.
This PR contains the following updates:
4.2→5.04.2→5.0=1.3.0→=2.0.01→28.0→9.0Release Notes
ZcashFoundation/ed25519-zebra (ed25519-zebra)
v5.0.0Compare Source
This release contains breaking changes, since the types of these
dependencies are part of the public API. The MSRV is unchanged (1.85).
rand_corefrom 0.6 to 0.10 (and theranddev-dependency from 0.8 to0.10).
SigningKey::new()andbatch::Verifier::verify()now require an RNGimplementing the
rand_core0.10CryptoRngtrait, e.g.rand::rng()fromrand0.10 (which replacesrand::thread_rng()).curve25519-dalekfrom 4 to 5.ed25519from 2 to 3 (and thussignaturefrom 2 to 3). The re-exporteded25519crate no longer has astdfeature.sha2from 0.10 to 0.11.pkcs8from 0.10 to 0.11 andderfrom 0.7 to 0.8 (pkcs8/pemfeatures).
pkcs8::Error::KeyMalformederrors now carry apkcs8::KeyError::Invalid, andSigningKeyimplementsTryFrom<pkcs8::PrivateKeyInfoRef>instead ofTryFrom<pkcs8::PrivateKeyInfo>.serdeencoding ofSignaturechanged (viaed255193): it now usesserdect, serializing as bytes in binary formats (bincode adds a lengthprefix) and as an uppercase hex string in human-readable formats. Signatures
serialized with 4.x cannot be deserialized with 5.0.
bourumir-wyngs/granit-parser (granit-parser)
v2.0.0Compare Source
commentsfeature. Disabling it compiles out scanner comment capture,parser and stack comment state, and the public comment types, variants, and
Options::max_buffered_comment_events, improving parsing performance by about 13%.YAML comments are still skipped and validated. Applications using
default-features = falsemust enable
commentsto accessComment,Placement, comment token/event variants, orOptions::max_buffered_comment_events.Options::emit_commentsremains available and defaults totruewith the feature enabled andfalsewithout it. Setting it totruehas no effect without the feature.Spannon-exhaustive so future releases can add source metadata. Construct spans withSpan::new,Span::empty, orSpan::default, use the metadata builders or field assignment,and include
..when destructuring. External struct literals and struct-update syntax areno longer supported.
SkipTabs::{Yes, No}policy andWhitespaceResultoutput. Custom
Inputimplementations must return(usize, Result<WhitespaceResult, ErrorKind>)from
skip_ws_to_eoland(usize, WhitespaceResult)fromskip_ws_to_eol_blanks.Replace
SkipTabs::Result(found_tabs, has_valid_yaml_ws)withWhitespaceResult::new(found_tabs, has_valid_yaml_ws); its result accessors are unchanged.Consumed-character counts, comment separation errors, and tab behavior are preserved.
Options::strict_indentation(defaultfalse) to require strict YAML-compliant indentationfor flow entries, delimiters, and scalar continuations (compliant with case 9C9N). Default behavior
is compatible with
PyYAMLandruamel.yaml.?as the last character of the input (it was rejected with"expected whitespace", while
?followed by a line break was accepted).(
a: "one\n two"). They were rejected with "invalid indentation in multiline quoted scalar".(
|\n a\n) no longer gains an extra line break ("a\n\n", now"a\n").SequenceEndspan of an indentless sequence (key:\n- a) is empty at the next token,instead of covering that token (
?of the next key).?in flow collections(
{?\ta: b}) and before block mapping scalar keys (?\tkey\n: value\nand? \tkey\n: value\n), as permitted by YAML 1.2.2. Tabs used as required indentation,including before compact block collections (
?\t-and?\tkey:), remain invalid.strict_indentationenabled, keep explicit-key tab indentation checks active across anchorand tag properties, including intervening comments. A key such as
?\t&a\n\tkey\n: value\nis rejected in strict mode because its content line lacks the required space indentation after
the anchor. The default relaxed mode preserves its acceptance of this input.
the last line has no line break, instead of moving them to column zero of a nonexistent next line.
comment without a final line break. Comment emission no longer changes these error coordinates.
strict_indentationalso checks the line after an escaped line break (\at the end of aline) in a double-quoted scalar in block context (
key: "a\thenb"at column 0).bourumir-wyngs/serde-saphyr (serde-saphyr)
v2.0.0Compare Source
YAML changes
discarding them (#236). Use a bare variant name, a tag with empty content, or a
tag followed by
~ornull; quoted strings and collections are rejected.Added
path_map::PathKind,PathKey::segments(), andPathMap::locations_for()for inspecting validation paths and resolving their YAML use/definition locations,
including best-effort spelling matches and recorded ancestor/root fallback.
RenderOptions::line_offsetandRenderOptions::source_namefor displayingembedded YAML diagnostics at their containing document's line numbers and naming
the root source in snippet headers, including the new
miette::to_miette_report_with_optionsentry point. Included files retain their ownnames and coordinates, and stored error locations and spans are unchanged.
PropertySyntax::DockerComposefor Compose-compatible property interpolation.commentsfeature, forwarding to granit-parser's matchingfeature. Builds with
default-features = falsemust enable it to useCommented<T>,CommentPosition, comment options, or comment budget fields and reports. Without it,YAML comments are still accepted and validated, but their text is not retained.
Options::non_finite_float_policywithNonFiniteFloatPolicy::{PassThrough, Reject, AsString}to configure non-finite floats delivered through
deserialize_any. Explicit policies overridethe legacy boolean; leaving the field unconfigured preserves its behavior.
borrowed_contextexample showing recursiveSerializeadapters that borrowan existing value tree and per-call formatting context, composing with
Tagged<T>andstyle wrappers without building a second container tree or using thread-local state.
SerializerOptions::no_lang_directive(defaultfalse) to suppress the%YAML 1.2directive and its leading---marker independently ofyaml_12's quoting.from_str_multiple,from_bytes_multiple, and their_with_optionsvariants todeserialize multiple YAML documents into any
C: Default + Extend<T>, including vectors,queues, sets, and custom accumulators. Values can borrow from the input string or UTF-8 byte
slice. Explicit type arguments specify both the document and collection types, for example
from_str_multiple::<String, Vec<_>>(input).error: Box<Error>field toError::AliasError, which keeps the original errorwhen an aliased value fails to deserialize. A custom
MessageFormatterorLocalizernow applies to that error, and
std::error::Error::sourcereturns it(#199).
Changed
from_multiple,from_multiple_with_options,from_slice_multiple, andfrom_slice_multiple_with_optionsnow acceptT: Deserialize<'de>so values can borrow fromthe input. They retain their names, single type parameter, and
Vec<T>returns and are notdeprecated. Ordinary calls, including
from_multiple::<Config>(input)and generic callerswith
T: DeserializeOwned, continue to work. Function pointers or callbacks accepting arbitraryinput lifetimes may need forwarding closures, such as
|input| from_multiple::<String>(input).serde-saphyr's
commentsfeature. Serialization-only builds remain independent ofgranit-parser, including when comment emission is enabled.
deserialize_any, including overflowingliterals such as
1e999. Opt intoPassThroughto preserve them in float-capable visitors,untagged enums, and flattened float fields, or
AsStringto receive canonical strings.With
PassThrough,serde_json::Valueconverts them toNullwithout an error.Direct
f32/f64deserialization is unchanged.Error::AliasErrorhas a new mandatoryerror: Box<Error>field.Manual constructors must supply it, and patterns listing every field must add
erroror...The variant name is unchanged. Rendering and
source()use the original error; thedeserializer still populates
msgwith anerror.to_string()snapshot for existing handlers.Deprecated
Options::reject_non_finite_typeless_floatin favor ofnon_finite_float_policy.When the new field is unconfigured, the boolean retains its original behavior:
true(the default) rejects and
falseconverts to strings. UseRejectorAsString, respectively,when migrating. Explicit policies override the boolean. Serialized options that omit both
fields retain the 1.3.0 behavior of converting non-finite floats to strings;
Options::default()continues to reject them.msgfield ofError::AliasErrorin favor of its structurederrorfield.Existing
Error::AliasError { msg, .. }patterns still work with a deprecation warning.Fixed
~,null,Null, andNULL.Other capitalization such as
NulLremains a string instead of being rejected, convertedto an empty value, or skipped as a document (#234).
LastWinsvalues and inline merges no longer produce alias errors when noalias was used. Replay preserves per-node origins, including genuine nested aliases,
ordinary value locations, and merge use-sites for
Spanned<T>.strict_booleans: truenow recognizes only the six YAML 1.2 Core boolean spellings.Other capitalization such as
tRuEremains a string during inference, is acceptedas unquoted text with
no_schema, and is rejected for boolean targets.(used at line X, column Y).The new
Localizer::alias_used_athook controls this suffix independently of failure anddefinition locations. Custom localizers that previously used
attach_locationto formator suppress alias-use coordinates should override
alias_used_atas well.include context. Validation messages honor external-message overrides, and multi-document
summaries honor custom message formatters. English defaults are unchanged.
Custom
Localizerimplementations migrating from 1.x must also overrideanchor_defined_hereto translate the alias anchor-definition label.(defined)or(defined here), including errors in included YAML files.Error::SerdeInvalidLengthwith separatelen,expected, andlocationfields, allowing custom formatters to inspect them.Default diagnostic wording is preserved (#205, item 6).
Localizer::root_path_labelin plain, snippet, andmiettediagnostics (#205, item 5c).characters inside each issue. Built-in formatters use the new optional
MessageFormatter::format_validation_issue_lineshook; existing custom whole-messageoverrides retain their behavior (#205, item 5a).
outer anchor location while exposing the original error directly through
error,source(),and the legacy
msgfield (#205, item 1).including fields outside the anchor's snippet window. Plain messages, snippets, and
miettereports include the distinct failing location; equal locations are not repeated.
MessageFormatter, includingformatters that delegate other variants to the built-in formatter. Plain messages report
the alias definition and use locations once through the active
Localizer; snippet andmiettediagnostics use location labels without embedding plain-text location suffixes.Custom location formatting and suppression now apply throughout aliased values
(#199).
std::error::Error::sourceexposes the inner error for bothError::AliasErrorandError::WithSnippet, preserving the source chain through the default snippet wrapper.huge_documentsandserde_derived_typesenabledeserialize, fixing isolated featurebuilds with
--no-default-features, including autopkgtests of Debian team (as observed).Documentation
serde_yamlmigration caveat for null values inStringfields,including when to use
Option<String>, quoted strings, or!!str(#229).
zip-rs/zip2 (zip)
v9.1.3Compare Source
🚀 Features
🐛 Bug Fixes
⚡ Performance
v9.1.2Compare Source
🐛 Bug Fixes
v9.1.1Compare Source
🐛 Bug Fixes
v9.1.0Compare Source
🚀 Features
innermethod to reader wrappers (#1050)🐛 Bug Fixes
🚜 Refactor
⚡ Performance
⚙️ Miscellaneous Tasks
Bench
v9.0.5Compare Source
🐛 Bug Fixes
⚙️ Miscellaneous Tasks
v9.0.4Compare Source
🐛 Bug Fixes
Ok(None)when read_zipfile_from_stream is called on an empty archive (#1063)⚙️ Miscellaneous Tasks
v9.0.3Compare Source
🐛 Bug Fixes
v9.0.2Compare Source
🐛 Bug Fixes
v9.0.1Compare Source
🐛 Bug Fixes
v9.0.0Compare Source
🚀 Features
by_index_with_data_descriptor(#994)ZipWriter::hide_filefor in-place entry deletion (#924)aes_modetoaes_settings()in ZipFileData (#925)🐛 Bug Fixes
🚜 Refactor
ZipFileFlagsto wrapflags(#947)crate::formatwithzip::unstable::format(#944)format/functions.rs(#943)make_reader()function (#936)initialize_local_block(#934)write/options.rs(#931)⚙️ Miscellaneous Tasks
Fix
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.