Skip to content

chore(deps): update rust - #638

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rust
Open

chore(deps): update rust#638
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/rust

Conversation

@renovate

@renovate renovate Bot commented Mar 31, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
cucumber dev-dependencies minor 0.220.23
cucumber workspace.dependencies minor 0.220.23
indexmap dependencies patch 2.14.02.14.1
owo-colors dependencies minor 4.3.04.4.0
serde-saphyr workspace.dependencies minor 1.1.01.2.0
usage-lib (source) dependencies minor 6.1.16.6.0

Release Notes

cucumber-rs/cucumber (cucumber)

v0.23.0

Compare Source

Diff | Milestone

BC Breaks
  • Fixed precedence of operations in tag expressions to align with upstream. (gherkin#52, gherkin#51)
Changed
  • Upgraded [gherkin] crate to 0.16 version. (0d544772)
  • Allowed And-like and But-like keywords at the beginning of Scenario, automatically considering them as Given-type steps. (gherkin#53)
indexmap-rs/indexmap (indexmap)

v2.14.1

Compare Source

  • Simplify comparisons where Equivalent isn't needed (Q = K).
  • Unify index assertions for bounds checks.
  • Fix (or expect) clippy lints.
owo-colors/owo-colors (owo-colors)

v4.4.0

Compare Source

Changed
  • Updated MSRV to Rust 1.83. Thanks Expyron for your first contribution!
bourumir-wyngs/serde-saphyr (serde-saphyr)

v1.2.0

Compare Source

Changed
  • Folded property-interpolation depth and work limits into Budget; property resource-limit
    failures are now reported through Error::Budget and BudgetBreach.
  • Added the opt-in Options::reject_unsupported_tags strict mode. It rejects explicitly tagged
    scalar, sequence, and mapping nodes when their tag is unknown to serde-saphyr; the default remains
    permissive for compatibility with custom tagged enums. YAML 1.1 !!merge and !!value are
    accepted in this mode only as the exact scalar mapping keys << and =, respectively, while
    robotics-only !degrees and !radians require both the robotics crate feature and
    angle_conversions, and !include requires both the include crate feature and a configured
    resolver.
  • Enforced the scalar, sequence, or mapping node kinds required by recognized tags even when
    reject_unsupported_tags is disabled.
  • Hardened serializer indentation handling: indent_step is now limited to 1..=64, all
    serializer entry points validate it, and indentation arithmetic returns an error instead of
    overflowing. We do not consider this breaking because values outside this range does not look sane.
  • Validated custom anchor-generator names before emission. Names must be 1–256 bytes and cannot
    contain whitespace, control characters, or YAML flow punctuation; unsupported names now return
    a serialization error.
Fixes
  • Recognized explicit YAML 1.1 !!merge keys, including verbatim tags and %TAG-expanded
    handles, everywhere implicit << merge keys are supported.
  • Recognized the YAML 1.1 !!value tag while intentionally treating it as a no-op annotation.
  • Accepted valid zero-indented root folded block scalars, including #-prefixed content lines.
  • Fixed externally tagged typetag trait-object deserialization by consuming the closing mapping
    event when a Serde map visitor returns after its final key/value pair, preventing a false
    "multiple YAML documents" error.
  • Rejected non-UTF-8 canonical include and root-file paths before resolver policy checks and source
    identity handling, preventing lossy path collisions and policy bypasses on Unix.
  • Reported alias-use locations as primary for unsupported-tag and budget failures during replay,
    while retaining the anchor-definition locations as secondary context.
Testing
  • Reviewed yaml test suite, made sure all 350 active IDs and all 402 active cases are represented and documented
    we use YAML Test Suite v2022-01-17.
  • property test with 1,024 generated cases to check the round trip.
  • added tests for typetag.
jdx/usage (usage-lib)

v6.6.0

Compare Source

🚀 Features

v6.5.0

Compare Source

🚀 Features
🐛 Bug Fixes
New Contributors

v6.4.1

Compare Source

🐛 Bug Fixes
🔍 Other Changes
📦️ Dependency Updates

v6.4.0

Compare Source

🚀 Features
🐛 Bug Fixes
🚜 Refactor

v6.3.0

Compare Source

🚀 Features
  • (spec) render heading prose in the Go help renderer by @​jdx in #​1290
🐛 Bug Fixes

v6.2.0

Compare Source

🚀 Features
🐛 Bug Fixes
  • (completion) handle attached values and emit built-ins by @​jdx in #​1277
  • (derive) preserve flattened command metadata by @​jdx in #​1268
  • (derive) skip choice checks for typed defaults by @​jdx in #​1269
  • (derive) suppress generated partial field lint by @​jdx in #​1278
  • (derive) keep an invalid choice after an override displaces the flag by @​jdx in #​1286
  • (spec) make the two KDL writers agree on three more nodes by @​jdx in #​1289
🚜 Refactor
⚡ Performance
🛡️ Security
🔍 Other Changes
New Contributors

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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

renovate Bot commented Mar 31, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package serde-saphyr@1.1.0 --precise 1.2.0
error: failed to load manifest for workspace member `/tmp/renovate/repos/github/finos/morphir/crates/integration-tests`
referenced via `crates/*` by workspace at `/tmp/renovate/repos/github/finos/morphir/Cargo.toml`

Caused by:
  failed to load manifest for dependency `morphir-common`

Caused by:
  failed to read `/tmp/renovate/repos/github/finos/morphir/ecosystem/morphir-rust/crates/morphir-common/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/integration-tests/Cargo.toml --workspace
error: failed to load manifest for workspace member `/tmp/renovate/repos/github/finos/morphir/crates/integration-tests`
referenced via `crates/*` by workspace at `/tmp/renovate/repos/github/finos/morphir/Cargo.toml`

Caused by:
  failed to load manifest for dependency `morphir-common`

Caused by:
  failed to read `/tmp/renovate/repos/github/finos/morphir/ecosystem/morphir-rust/crates/morphir-common/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/morphir/Cargo.toml --package indexmap@2.14.0 --precise 2.14.1
error: failed to load manifest for workspace member `/tmp/renovate/repos/github/finos/morphir/crates/integration-tests`
referenced via `crates/*` by workspace at `/tmp/renovate/repos/github/finos/morphir/Cargo.toml`

Caused by:
  failed to load manifest for dependency `morphir-common`

Caused by:
  failed to read `/tmp/renovate/repos/github/finos/morphir/ecosystem/morphir-rust/crates/morphir-common/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

@netlify

netlify Bot commented Mar 31, 2026

Copy link
Copy Markdown

Deploy Preview for angry-raman-7c44f6 canceled.

Name Link
🔨 Latest commit 4ce650a
🔍 Latest deploy log https://app.netlify.com/projects/angry-raman-7c44f6/deploys/6a94e68443444500086a7fba

@renovate
renovate Bot force-pushed the renovate/rust branch from ed8dab3 to 96b1eb6 Compare April 2, 2026 19:35
@renovate
renovate Bot force-pushed the renovate/rust branch from 96b1eb6 to 2bbae09 Compare April 28, 2026 05:13
@renovate
renovate Bot force-pushed the renovate/rust branch 3 times, most recently from 9ac1a70 to 7445797 Compare June 23, 2026 01:07
@renovate
renovate Bot force-pushed the renovate/rust branch 2 times, most recently from 784aef0 to 2bc11d5 Compare July 8, 2026 04:45
@renovate
renovate Bot force-pushed the renovate/rust branch from 2bc11d5 to 1762af9 Compare July 10, 2026 10:57
@renovate renovate Bot changed the title chore(deps): update rust fix(deps): update rust Jul 10, 2026
@renovate
renovate Bot force-pushed the renovate/rust branch from 1762af9 to bd9237d Compare July 27, 2026 14:29
@renovate
renovate Bot force-pushed the renovate/rust branch 3 times, most recently from 04eb66d to 788151d Compare August 17, 2026 10:00
@renovate
renovate Bot force-pushed the renovate/rust branch 5 times, most recently from ac3e535 to 0a94f83 Compare August 17, 2026 20:57
@renovate
renovate Bot force-pushed the renovate/rust branch 6 times, most recently from 2cc1ddd to 699c82e Compare August 24, 2026 00:31
DamianReeves added a commit that referenced this pull request Aug 24, 2026
…679)

Takes the dependency updates from the renovate/rust branch (#638) and
carries them to green, which that PR could not do on its own: Renovate's
Cargo.lock regeneration was failing with "Artifact file update failure",
so it shipped manifest bumps with no matching lockfile.

That artifact failure was caused by the toml_datetime conflict fixed in
#677. With the lockfile resolvable again, a full `cargo update` reaches
a better state than the workaround in #677 did:

  extism           1.13.0 -> 1.30.0  (now matched with extism-manifest)
  extism-manifest  1.13.0 -> 1.30.0
  wasmtime         37.0.3 -> 43.0.2

wasmtime 43 does not require toml_datetime >= 0.6.5, so the conflict
that forced #677 to downgrade proc-macro-crate to 2.0.0 no longer
arises. That downgrade is dropped and proc-macro-crate returns to stock
2.0.2. The extism fix is now structural rather than a pinned
workaround.

starbase 0.10 -> 0.13 required a source migration, the only breakage in
the whole refresh:

  - AppResult gained a generic error parameter. 0.10 defined it as
    miette::Result<Option<u8>>, so AppResult<miette::Report> preserves
    the previous semantics exactly. 23 return types across 12 files.
  - AppSession gained an associated Error type.
  - MainResult is now behind an opt-in "miette" feature; enabled it.
  - App::run returns AppRunOutcome instead of a Result.
    into_miette_result() preserves the real exit code, where the old
    `?` path went through miette's default of always exiting 1.

Verified locally against the committed lockfile with --locked, matching
what CI now enforces. All ten checks pass: fmt, clippy -D warnings,
tests, and release builds for both morphir and morphir-live, including
the morphir-live desktop build.
@renovate
renovate Bot force-pushed the renovate/rust branch 29 times, most recently from cd712b2 to 9e43d15 Compare August 29, 2026 04:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant