fix(deps): update rust-crate-deps-bumps (major)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
ed25519-dalek (source)	dependencies	major	2.1 → 3.0
schemars (source)	build-dependencies	major	0.8 → 1.0
syn	build-dependencies	major	2 → 3
syn	build-dependencies	major	2.0 → 3.0

---

Release Notes

dalek-cryptography/curve25519-dalek (ed25519-dalek)

v3.0.0

Breaking Changes

• Update edition to 2024
• Update the MSRV from 1.60 to 1.85
• Remove std feature now that error::Error is in core
• Make signing and verifying keys use pkcs8::spki::SignatureAlgorithmIdentifier instead of DynSignatureAlgorithmIdentifier (#​779)
• Upgrade ed25519 dependency to v3.0.0
• Upgrade signature dependency to v3.0.0
• Upgrade sha2 and sha3 dependencies to v0.11
• Upgrade getrandom dependency to v0.4
• Upgrade chacha20 dependency to v0.10
• Upgrade rand_core dependency to v0.10.0

Other Changes

• Re-export rand_core (#​908)
• Add allocation-free EdwardsPoint::compress_batch (#​832)
• Add strobe-rs dependency and delete vendored STROBE impl (#​895)
• Impl MultipartSigner and MultipartVerifier for SigningKey and VerifyingKey (#​764)
• Impl KeySizeUser, TryKeyInit, and Generate for SigningKey. Also impl KeySizeUser for VerifyingKey #​733

GREsau/schemars (schemars)

v1.2.2

Compare Source

• Update to syn 3 in schemars_derive

v1.2.1

Compare Source

Fixed

• transform attributes are now applied after the schema is otherwise fully constructed. In particular, they're now applied after all other attributes are processed. (#​505)

v1.2.0

Compare Source

Added

• Add smol_str03 feature (#​486)

Changed

• Schemas generated for HashMap/BTreeMap with enum keys are now more specific (#​452)

v1.1.0

Compare Source

Added

• Public functions that have no side-effects are now marked with #[must_use] so that they report a lint warning when the returned value is unused, as this likely indicates a mistake.

Fixed

• Improve accuracy of schemas for flattened enums, in particular: unit variants of externally-tagged enums, and enums wrapped in Option<>. (#​464 / #​483)

v1.0.5

Compare Source

Fixed

• Fix schema.pointer_mut() to resolve URI fragment identifiers like #/$defs/foo, matching current behaviour of schema.pointer() (#​478 / #​479)

v1.0.4

Compare Source

Fixed

• Fix JsonSchema impl on atomic types being ignored on non-nightly compilers due to a buggy cfg check (#​453)
• Fix compatibility with minimal dependency versions, e.g. old(-ish) versions of syn (#​450)
• Fix derive for empty tuple variants (#​455)

v1.0.3

Compare Source

Fixed

• Fix compile error when a doc comment is set on both a transparent (or newtype) struct and its field (#​446)
• Fix json_schema!() macro compatibility when used from pre-2021 rust editions (#​447)

v1.0.2

Compare Source

Fixed

• Fix schema properties being incorrectly reordered during serialization (#​444)

v1.0.1

Compare Source

Fixed

• Deriving JsonSchema with no_std broken due to std::borrow::ToOwned trait not being in scope (#​441)

v1.0.0

Compare Source

This is a major release with many additions, fixes and changes since 0.8 (but not many since 0.9). While the basic usage (deriving JsonSchema and using schema_for!() or SchemaGenerator) is mostly unchanged, you may wish to consult the migration guide which covers some of the most significant changes.

Changes since 1.0.0-rc.2:

Added

• #[schemars(bound = ...)] attributes are now used from fields as well as containers
• The Schema::pointer(...) method now works when given a JSON pointer in URI Fragment representation with a leading # character. In particular, this means that you can now lookup a schema from a $ref value using that method.

Fixed

• Schema names that contain special characters are now correctly encoded when used inside a $ref value (#​436)
• Optimise type param usage in SchemaGenerator::subschema_for, reducing LLVM line count and improving compile times (#​439)

v0.9.0

Compare Source

This version is identical to 1.0.0-alpha.18, but is available for those who are unable to unwilling to use a pre-release version.

Those upgrading from Schemars 0.8 may want to consult the migration guide, which also applies when migrating from 0.8 to 0.9.

dtolnay/syn (syn)

v3.0.4

Compare Source

• Allow safe fn in impl Parse for ForeignItemFn (#​2078)

v3.0.3

Compare Source

• Documentation improvements

v3.0.2

Compare Source

• Add Error::new_range(start..end, "msg") (#​2068, #​2070)
• Add Cursor::prev_span

v3.0.1

Compare Source

• Parse const traits (#​2056, #​2057, #​2058, #​2063, #​2064)
• Parse unsafe binder types (#​2065)
• Parse impl restrictions (#​2066)

v3.0.0

Compare Source

This release contains adjustments to the syntax tree to account for ongoing Rust language development from the 3 years since syn 2.0.0 and to anticipate some in-flight Rust language RFCs.

These include: default values in fields, pinned type sugar, raw lifetimes, generator blocks and functions, unnamed enum variants, attributes in tuple types and tuple patterns, named arguments in parenthesized generic argument lists, lightweight clones, const traits, const function pointers, mutability restricted fields, supertrait auto implementation, final associated functions, trait implementability restrictions, const blocks in path arguments, item-level const blocks, return type notation, never patterns, function delegation, mutable by-reference bindings, in-place initialization, field projections, explicitly dyn-compatible traits, view types, file-level frontmatter, generic const arguments, guard patterns, lazy type aliases, explicitly safe foreign items, super let, unsafe fields, pattern types, heterogeneous try-blocks, function contracts, async function trait bounds, static closure coroutine syntax, unsafe binder types, move expressions, for-await loops, and postfix keywords.

[API documentation for 3.0]

Breaking changes

Modifiers

To reserve more room for language evolution, there are 10 new non-exhaustive structs in the syntax tree having the following commonality:

• Name ending in Modifiers. {BlockModifiers, ClosureModifiers, ConstModifiers, FieldModifiers, FnModifiers, ImplModifiers, LocalModifiers, TraitBoundModifiers, TraitModifiers, TypeModifiers}

• Each implements Default. The default value is guaranteed to comprise no tokens.

• Non-exhaustive. Can only be instantiated by Syn's parser or by creating and then mutating ▁▁Modifiers::default().

• Does not implement Parse. When parsing, they are parsed by the enclosing syntax tree node.

• Does not implement ToTokens. In some cases the syntax that these nodes might hold in the future is not necessarily contiguous tokens.

• Provides .require_empty() -> Result<()> which returns a meaningfully spanned error if the modifiers are different from the empty default. This enables a caller to reject syntax it does not recognize without knowing what that syntax may be.

Types

• Type::BareFn has been renamed to Type::FnPtr to mirror the compiler's terminology. Together with this, BareVariadic is renamed to FnPtrVariadic.

• The mutually exclusive const_token and mutability fields of Type::Ptr have been unified into an enum of type PointerMutability, which was already previously used by Expr::RawAddr.

• Every Type variant now holds attributes, which can represent the attributes of element types inside a tuple type, or attributes for a function return type.

• BareFnArg is renamed to NamedArg and is used in ParenthesizedGenericArguments, in addition to the existing use in Type::FnPtr.

Expressions

• In Expr::Closure, the fields or1_token and or2_token have been renamed to inputs_begin and inputs_end to indicate the beginning and ending | token of the closure inputs.

Statements

• Attributes are now preserved on all expression kinds in statement position. Previously, parsing would silently lose attributes on some expression statements without a dedicated Expr variant, such as tail-call expressions.

Patterns

• The guard field of Arm is replaced by a new Pat::Guard variant held in the arm's pat.

Items

• The unsafety field of Signature, which represented the presence or absence of unsafe, is replaced by a 3-way Safety enum which may be safe, unsafe, or default. ForeignItem::Static also gets a Safety.

• Some of the fields of Receiver have been split to a non-exhaustive ReceiverKind enum to create room for proposed new kinds of method receivers, such as pinned.

• Type aliases now hold a WhereClausePlacement to distinguish between early placement (which is the default for item-level type aliases and is deprecated in associated type aliases) and late placement (which is the default for associated type aliases and is unstable in item-level type aliases). Parsing and printing a syntax tree will now preserve the where-clause placement rather than rewriting it to the default placement for the item kind.

Generics

• WherePredicate::Lifetime and WherePredicate::Type have a new field holding the attributes on the where-predicates.

• GenericParam::Type and GenericParam::Const now match the rest of the syntax tree in holding their optional default using a single Option of tuple, rather than a pair of Option.

Literals

• The Parse implementation of Lifetime no longer permits keyword lifetimes, matching a change in Rust 1.81 to deny such lifetimes pre-expansion. Lifetime::parse_any may be used to parse lifetimes permissive of keywords.

• LitInt and LitFloat no longer implement From<proc_macro2::Literal>. Use Lit::new(literal) and then match Lit::Int or Lit::Float.

• The StrStyle enum was unused and has been deleted.

More

• File contains a new Option<Frontmatter>, but does not yet parse frontmatter in syn::parse_file until that language feature progresses closer to stabilization.

• Some enums no longer provide From impls. Construct the variant by name instead, such as Expr::Array(e) in place of e.into().

• The pop method of Punctuated<T, P> now returns Option<T> discarding the trailing punctuation if any, rather than Option<Pair<T, P>>. A new method pop_pair provides the old behavior.

• Syntax tree traversal (visit, visit_mut, fold) no longer provides a method for processing Span. This was already incompletely supported and never walked most of the spans in a syntax tree.

• The Speculative and AnyDelimiter traits have been sealed and cannot be implemented for types outside of Syn's ParseStream.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 8am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: rust/Cargo.toml

Artifact update for syn resolved to version 3.0.4, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 3.0.3
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

File name: wasm/Cargo.toml

Artifact update for syn resolved to version 3.0.4, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 3.0.3
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/