Skip to content

fix(deps): update rust - #638

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

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

Conversation

@renovate

@renovate renovate Bot commented Mar 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
anyhow workspace.dependencies patch 1.0.100 → 1.0.104
async-trait dependencies patch 0.1.89 → 0.1.91
chrono build-dependencies patch 0.4.43 → 0.4.45
clap workspace.dependencies minor 4.5.57 → 4.6.5
dioxus (source) workspace.dependencies patch 0.7.3 → 0.7.10
gloo-timers (source) workspace.dependencies minor 0.3 → 0.4
indexmap dependencies minor 2.13.0 → 2.14.0
js-sys (source) dependencies patch 0.3.85 → 0.3.103
owo-colors dependencies minor 4.2.3 → 4.3.0
ratatui (source) workspace.dependencies patch 0.30.0 → 0.30.2
schemars (source) dependencies patch 1.2.1 → 1.2.2
serde (source) dependencies patch 1.0.228 → 1.0.229
serde (source) workspace.dependencies patch 1.0.228 → 1.0.229
serde_json dependencies patch 1.0.149 → 1.0.151
serde_json workspace.dependencies patch 1.0.149 → 1.0.151
starbase workspace.dependencies minor 0.10 → 0.13
tempfile (source) dev-dependencies minor 3.24.0 → 3.27.0
termimad dependencies minor 0.34 → 0.35
thiserror workspace.dependencies patch 2.0.18 → 2.0.19
tokio (source) dependencies minor 1.49.0 → 1.53.1
toml workspace.dependencies patch 0.9.11+spec-1.1.0 → 0.9.12
tracing-appender (source) workspace.dependencies patch 0.2.4 → 0.2.5
tracing-subscriber (source) workspace.dependencies patch 0.3.22 → 0.3.23
usage-lib (source) dependencies minor 2.16.1 → 2.18.2
wasm-bindgen (source) dependencies patch 0.2.108 → 0.2.126
web-sys (source) dependencies patch 0.3.85 → 0.3.103

Release Notes

dtolnay/anyhow (anyhow)

v1.0.104

Compare Source

  • Update syn dev-dependency to version 3

v1.0.103

Compare Source

  • Fix Stacked Borrows violation (UB) in Error::downcast_mut (#​451, #​452)

v1.0.102

Compare Source

v1.0.101

Compare Source

dtolnay/async-trait (async-trait)

v0.1.91

Compare Source

v0.1.90

Compare Source

  • Update to syn 3
chronotope/chrono (chrono)

v0.4.45: 0.4.45

Compare Source

What's Changed

v0.4.44: 0.4.44

Compare Source

What's Changed

clap-rs/clap (clap)

v4.6.5

Compare Source

v4.6.4

Compare Source

Internal
  • Update to syn v3

v4.6.3

Compare Source

Fixes
  • (derive) Allow "literal".function() as attribute values

v4.6.2

Compare Source

Fixes
  • (help) Say alias when there is only one

v4.6.1

Compare Source

Fixes
  • (derive) Ensure rebuilds happen when an read env variable is changed

v4.6.0

Compare Source

Compatibility
  • Update MSRV to 1.85

v4.5.61

Compare Source

Internal
  • Update dependencies

v4.5.60

Compare Source

Fixes
  • (help) Quote empty default values, possible values

v4.5.59

Compare Source

Fixes
  • Command::ignore_errors no longer masks help/version on subcommands

v4.5.58

Compare Source

DioxusLabs/dioxus (dioxus)

v0.7.10

Compare Source

What's Changed

  • [v0.7] Fix hotpatching when the bin target's crate name differs from the package name by @​nicoburns in #​5720

Full Changelog: DioxusLabs/dioxus@v0.7.9...v0.7.10

v0.7.9

Compare Source

This release fixes an issue where dx --version would use an outdated git SHA, and dioxus-cli installed from cargo install would not have a version at all, preventing self-update from functioning properly.

Full Changelog: DioxusLabs/dioxus@v0.7.8...v0.7.9

v0.7.8

Compare Source

This release fixes a few small bugs discovered while working on v0.8. We decided the backport these to bring out fixes faster.

What's Changed

Full Changelog: DioxusLabs/dioxus@v0.7.7...v0.7.8

v0.7.7

Compare Source

This release fixes a regression with JS bundling where DX would always bundle JS snippets as ESM, even though they might be CJS, UMD, or a generic JS snippet. We now properly detect the js module type and then run esbuild with the appropriate flags.

What's Changed

Full Changelog: DioxusLabs/dioxus@v0.7.6...v0.7.7

v0.7.6

Compare Source

Dioxus v0.7.6

This release solves a large number of bugs and adds a few new features! We intend for it to be the final release of 0.7 - our git repo will now ship breaking changes in prep for 0.8.

  • Shell-completions for dx using dx completions
  • Much faster dev server starts for dx serve --hotpatch
  • Dioxus web apps that panic while handling events will no longer brick the webpage
  • 20+ new code examples
  • cursor editor debug support
  • Windows app icon bundling in dx serve and dx bundle

What's Changed

New Contributors

Full Changelog: DioxusLabs/dioxus@v0.7.5...v0.7.6

v0.7.5

Compare Source

Dioxus v0.7.5

This release fixes a critical issue where Dioxus wouldn't compile if your Cargo.lock specified too-old versions dependencies like futures-unordered. This was caused by the Dioxus Cargo.toml specifying versions like futures="0.3" when in fact 0.3.32 was required.

Note that the dioxus crate was not updated - only its dependencies that use these versions - so we recommend running cargo update manually.

We also fixed a few other bugs related to hotpatching, autoformatting, and bundling.

What's Changed

New Contributors

Full Changelog: DioxusLabs/dioxus@v0.7.4...v0.7.5

v0.7.4

Compare Source

Dioxus 0.7.4

This release adds a few new features and fixes several bugs:

  • You can now customize all aspects of iOS and Android builds via Dioxus.toml. We are still updating docs on how this works, but for now, you can reference the new toml schema on which fields are available. https://github.com/DioxusLabs/dioxus/blob/main/packages/cli/schema.json
  • We have added a new FFI interface for Kotlin, Java, and Swift. We plan to add TS/JS next. This automatically bundles relevant source files into your project and generates Rust interfaces, making it easy to write native plugins.
  • We now support bundling iOS widgets, enabling things like live-activity support.
  • We have fixed, tested, and improved dx bundle by vendoring and inlining the tauri bundle code which we previously relied on. This properly sets paths for assets, fixing some long-standing bugs.
  • Many bugs and panics have been fixed! See "what's changed" for more.

What's Changed

New Contributors

Full Changelog: DioxusLabs/dioxus@v0.7.3...v0.7.4

rustwasm/gloo (gloo-timers)

v0.4.0

Compare Source

indexmap-rs/indexmap (indexmap)

v2.14.0

Compare Source

  • MSRV: Rust 1.85.0 or later is now required.
  • Updated the hashbrown dependency to 0.17.
  • Made more map::Slice methods const: new_mut, first_mut, last_mut,
    split_at_mut, split_at_mut_checked, split_first_mut, split_last_mut

v2.13.1

Compare Source

  • Made some Slice methods const:
    • map::Slice::{first,last,split_at,split_at_checked,split_first,split_last}
    • set::Slice::{first,last,split_at,split_at_checked,split_first,split_last}
owo-colors/owo-colors (owo-colors)

v4.3.0

Compare Source

Fixed
  • Scripts in the scripts/ directory are no longer published in the crate package. Thanks weiznich for your first contribution!
Changed

  • Mark methods with #[rust_analyzer::completions(ignore_flyimport)] and the OwoColorize trait with #[rust_analyzer::completions(ignore_flyimport_methods)]. This prevents owo-colors methods from being completed with rust-analyzer unless the OwoColorize trait is included.

    Unfortunately, this also breaks explicit autocomplete commands such as Ctrl-Space in many editors. (The language server protocol doesn't appear to have a way to differentiate between implicit and explicit autocomplete commands.) On balance we believe this is the right approach, but please do provide feedback on PR #​141 if it negatively affects you.

  • Updated MSRV to Rust 1.81.

ratatui/ratatui (ratatui)

v0.30.2

Compare Source

a gift

We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨‍🍳🐀

✨ Release highlights: https://ratatui.rs/highlights/v0302/

⚠️ List of breaking changes can be found here.

Features

  • 90639c1 (uncategorized) Add Termina backend by @joshka in #​2561

    Summary

    • add the ratatui-termina backend crate using the published termina
      crate
    • expose the backend through the termina feature and Ratatui
      prelude/backend re-exports
    • add a small Termina event-loop example and wire the backend into CI,
      xtask, README generation, and docs

    Refs #​1784

    Validation

    • cargo +nightly fmt
    • cargo check -p ratatui-termina --all-features --all-targets
    • cargo check -p ratatui --no-default-features --features termina
    • cargo check -p xtask
    • cargo check -p release-header
    • cargo xtask check-backend termina
    • cargo xtask test-backend termina
    • cargo xtask rdme --check
    • markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md .github/ISSUE_TEMPLATE/bug_report.md
Bug Fixes

  • fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #​2584

    Summary

    • require custom shadow effects to preserve the auto traits expected by
      Block-backed widgets
    • document the CellEffect auto-trait contract
    • add a public widget regression test for the affected ratatui::widgets
      re-exports

    Fixes #​2583

  • e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #​2587

    When a wide cell from the previous buffer is replaced by a short/normal
    cell, the trailing cell does not get an update if its content does not
    change. But if the wide cell has a background (or other) style, the
    terminal did render the trailing cell with that style.

    Force trailing cells to update if background, underline, or modifiers
    are different than the wide cell. We can ignore foreground.

    Fixes #​2585 (see that for the detailed visual reports)

  • 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #​2594

    Closes #​2582.

    Problem

    When the content is shorter than the viewport, the thumb is large
    relative to the track. With the position at the end, part_lengths
    clamped thumb_start to track_length - 1 while thumb_length was
    clamped independently to [1, track_length], so thumb_start + thumb_length could exceed track_length.

    bar_symbols lays out begin + track_start + thumb + track_end + end
    and zips it against the cells of the area. When the thumb overruns the
    track, track_end saturates to 0 but the thumb still emits more cells
    than the track can hold, so the trailing end symbol is pushed past the
    end of the area. The last visible cell ends up being a thumb (█) where
    the end arrow (▼) should be.

    Concretely, for the issue's repro (VerticalRight, content_length = 9, position = 8, height 24): track is 22, thumb_length = 17,
    thumb_start = 6, and 6 + 17 = 23 > 22.

    This is a regression from v0.30.0, where thumb_length was derived as
    thumb_end - thumb_start and therefore always fit within the track.

    Fix

    Clamp thumb_start to track_length - thumb_length (instead of
    track_length - 1) so the thumb always fits within the track and the
    end symbol is preserved.

    Test

    Two regression tests, both fail on main and pass with the fix:

    • thumb_stays_within_track_for_large_thumb_at_end checks
      part_lengths directly with the issue's parameters — asserts
      thumb_start + thumb_length <= track_length and that the parts sum to
      the track length.
    • render_scrollbar_keeps_end_symbol_for_large_thumb renders the #​2582
      case (both arrows, large thumb at the end) and asserts the end symbol is
      drawn rather than overwritten by a thumb cell.

    All existing scrollbar tests still pass.

Miscellaneous Tasks

  • c75d778 (ci) Add cargo-udeps dependency check by @joshka in #​2599

    Adds cargo xtask udeps and runs it from CI as a required job.

    This complements cargo-machete rather than replacing it. cargo-machete
    is a fast static source scan, which is why it missed the package-level
    unused deps fixed in #​2598 when the same dependency names were still
    referenced by example crates. cargo-udeps compiles the workspace and
    checks rustc dep-info, so it can catch unused dependency declarations
    for the package being checked.

    To make the new job pass, this also removes the remaining true-positive
    unused dev-deps and records explicit cargo-udeps ignores for current
    false positives / intentional cases: ratatui-core critical-section,
    ratatui-crossterm's duplicate crossterm version feature shape, and
    ratatui-termwiz's doc-example-only ratatui dev-dependency.

    I searched existing issues and PRs for udeps / cargo-udeps / "cargo
    udeps". I did not find prior ratatui discussion about adopting
    cargo-udeps; the only hits were Dependabot PR bodies for
    taiki-e/install-action release notes mentioning cargo-udeps version
    updates, for example #​1971, #​2095, #​2194, and #​2522.

    Validation:- cargo xtask udeps

    • cargo xtask format --check

  • 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #​2598

    Audit removes these dependencies that are not used:

    ratatui/Cargo.toml — Removed from [dev-dependencies]:

    • futures
    • rand_chacha
    • tokio
    • tracing
    • tracing-appender
    • tracing-subscriber

    ratatui-core/Cargo.toml — Moved from [dependencies] →
    [dev-dependencies]:

    • indoc
Continuous Integration

  • 36854ef (uncategorized) Add auto-merge required gate by @joshka in #​2596

    Summary

    This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
    happy with the change but CI is still running.

    The workflow change adds a single aggregate required job to the main
    CI workflow. The repository now has auto-merge
    enabled
    and an ensure checks pass
    ruleset
    that requires that required status context on main.

    Why

    Without a required status context, GitHub's auto-merge button is not
    useful for the maintainer flow we want. The goal is to let a maintainer
    review a PR, decide it is ready, click auto-merge, and move on without
    coming back later just to check whether the remaining jobs finished.

    This does not relax the merge policy. GitHub's own auto-merge behavior
    is to merge only after all required reviews and required status checks
    are satisfied. This change gives GitHub a stable required status to wait
    on automatically.

    Precedent

    I have been using this same auto-merge pattern in
    ratatui/tui-widgets, where
    it has worked well for the intended maintainer flow: once a PR looks
    ready, I can enable auto-merge and let GitHub merge it after the
    remaining checks and review requirements are satisfied.

    How it works

    The new required job depends on the main CI jobs in
    .github/workflows/ci.yml and always runs after them. It fails if any
    required dependency fails, is cancelled, or is skipped.

    The repository ruleset requires only this aggregate required context
    instead of requiring every individual matrix job separately. That gives
    GitHub one stable status to wait on while preserving the existing CI
    coverage.

    Things to know

    • Auto-merge is opt-in per PR. Maintainers still choose when to click
      it.
    • It does not skip review requirements, status checks, labels, or any
      other protection rule.
    • A PR with auto-merge enabled can still show as blocked while checks or
      required reviews are pending. That is expected.
    • If something needs to merge normally, maintainers can still use the
      regular merge path or an allowed ruleset bypass. This is a convenience
      path, not a hard blocker.
    • Existing open PRs may need a rebase or synchronize event after this
      lands so they pick up the new required workflow job.
    • If a new required CI job is added later, it should be added to the
      required.needs list or it will not be represented by the aggregate
      gate.
    • Jobs that are intentionally allowed to fail should be handled
      carefully before adding them to required.needs, because skipped,
      cancelled, and failed dependencies make the aggregate fail.

    Current PR state

    Auto-merge is already enabled on this PR. If you approve it and the
    required checks pass, GitHub will squash-merge it automatically;
    approving it is enough to let the PR merge once the remaining
    requirements are satisfied.

    GitHub docs

    Validation

    • ruby -e 'require "yaml"; YAML.load_file(".github/workflows/ci.yml"); puts "ok"'
    • actionlint .github/workflows/ci.yml
    • Verified ratatui/ratatui has allow_auto_merge: true
    • Verified the active ensure checks pass ruleset requires status
      context required
    • Verified this PR has squash auto-merge enabled and is blocked pending
      checks/review
New Contributors
  • @satyakwok made their first contribution in #​2594
  • @KikiKian made their first contribution in #​2598

Full Changelog: ratatui/ratatui@ratatui-v0.30.1...ratatui-v0.30.2

v0.30.1

Compare Source

a gift

We are excited to announce the new version of ratatui - a Rust library that's all about cooking up TUIs 👨‍🍳🐀

✨ Release highlights: https://ratatui.rs/highlights/v0302/

⚠️ List of breaking changes can be found here.

Features

  • 90639c1 (uncategorized) Add Termina backend by @joshka in #​2561

    Summary

    • add the ratatui-termina backend crate using the published termina
      crate
    • expose the backend through the termina feature and Ratatui
      prelude/backend re-exports
    • add a small Termina event-loop example and wire the backend into CI,
      xtask, README generation, and docs

    Refs #​1784

    Validation

    • cargo +nightly fmt
    • cargo check -p ratatui-termina --all-features --all-targets
    • cargo check -p ratatui --no-default-features --features termina
    • cargo check -p xtask
    • cargo check -p release-header
    • cargo xtask check-backend termina
    • cargo xtask test-backend termina
    • cargo xtask rdme --check
    • markdownlint-cli2 ARCHITECTURE.md ratatui-termina/README.md .github/ISSUE_TEMPLATE/bug_report.md
Bug Fixes

  • fce3c80 (widgets) Require thread-safe shadow effects by @joshka in #​2584

    Summary

    • require custom shadow effects to preserve the auto traits expected by
      Block-backed widgets
    • document the CellEffect auto-trait contract
    • add a public widget regression test for the affected ratatui::widgets
      re-exports

    Fixes #​2583

  • e306ce6 (buffer) Create updates for "uncovered" cells by @benjajaja in #​2587

    When a wide cell from the previous buffer is replaced by a short/normal
    cell, the trailing cell does not get an update if its content does not
    change. But if the wide cell has a background (or other) style, the
    terminal did render the trailing cell with that style.

    Force trailing cells to update if background, underline, or modifiers
    are different than the wide cell. We can ignore foreground.

    Fixes #​2585 (see that for the detailed visual reports)

  • 81e667f (scrollbar) Keep a large thumb within the track at the end by @satyakwok in #​2594

    Closes #​2582.

    Problem

    When the content is shorter than the viewport, the thumb is large
    relative to the track. With the position at the end, part_lengths
    clamped thumb_start to track_length - 1 while thumb_length was
    clamped independently to [1, track_length], so thumb_start + thumb_length could exceed track_length.

    bar_symbols lays out begin + track_start + thumb + track_end + end
    and zips it against the cells of the area. When the thumb overruns the
    track, track_end saturates to 0 but the thumb still emits more cells
    than the track can hold, so the trailing end symbol is pushed past the
    end of the area. The last visible cell ends up being a thumb (█) where
    the end arrow (▼) should be.

    Concretely, for the issue's repro (VerticalRight, content_length = 9, position = 8, height 24): track is 22, thumb_length = 17,
    thumb_start = 6, and 6 + 17 = 23 > 22.

    This is a regression from v0.30.0, where thumb_length was derived as
    thumb_end - thumb_start and therefore always fit within the track.

    Fix

    Clamp thumb_start to track_length - thumb_length (instead of
    track_length - 1) so the thumb always fits within the track and the
    end symbol is preserved.

    Test

    Two regression tests, both fail on main and pass with the fix:

    • thumb_stays_within_track_for_large_thumb_at_end checks
      part_lengths directly with the issue's parameters — asserts
      thumb_start + thumb_length <= track_length and that the parts sum to
      the track length.
    • render_scrollbar_keeps_end_symbol_for_large_thumb renders the #​2582
      case (both arrows, large thumb at the end) and asserts the end symbol is
      drawn rather than overwritten by a thumb cell.

    All existing scrollbar tests still pass.

Miscellaneous Tasks

  • c75d778 (ci) Add cargo-udeps dependency check by @joshka in #​2599

    Adds cargo xtask udeps and runs it from CI as a required job.

    This complements cargo-machete rather than replacing it. cargo-machete
    is a fast static source scan, which is why it missed the package-level
    unused deps fixed in #​2598 when the same dependency names were still
    referenced by example crates. cargo-udeps compiles the workspace and
    checks rustc dep-info, so it can catch unused dependency declarations
    for the package being checked.

    To make the new job pass, this also removes the remaining true-positive
    unused dev-deps and records explicit cargo-udeps ignores for current
    false positives / intentional cases: ratatui-core critical-section,
    ratatui-crossterm's duplicate crossterm version feature shape, and
    ratatui-termwiz's doc-example-only ratatui dev-dependency.

    I searched existing issues and PRs for udeps / cargo-udeps / "cargo
    udeps". I did not find prior ratatui discussion about adopting
    cargo-udeps; the only hits were Dependabot PR bodies for
    taiki-e/install-action release notes mentioning cargo-udeps version
    updates, for example #​1971, #​2095, #​2194, and #​2522.

    Validation:- cargo xtask udeps

    • cargo xtask format --check

  • 4a63d41 (uncategorized) Remove unused dependencies by @KikiKian in #​2598

    Audit removes these dependencies that are not used:

    ratatui/Cargo.toml — Removed from [dev-dependencies]:

    • futures
    • rand_chacha
    • tokio
    • tracing
    • tracing-appender
    • tracing-subscriber

    ratatui-core/Cargo.toml — Moved from [dependencies] →
    [dev-dependencies]:

    • indoc
Continuous Integration

  • 36854ef (uncategorized) Add auto-merge required gate by @joshka in #​2596

    Summary

    This makes GitHub auto-merge usable for Ratatui PRs once maintainers are
    happy with the change but CI is still running.

    The workflow change adds a single aggregate required job to the main
    CI workflow. The repository now has auto-merge
    enabled
    and an ensure checks pass
    ruleset
    that requires that required status context on main.

    Why

    Without a required status context, GitHub's auto-merge button is not
    useful for the maintainer flow we want. The goal is to let a maintainer
    review a PR, decide it is ready, click auto-merge, and move on without
    coming back later just to check whether the remaining jobs finished.

    This does not relax the merge policy. GitHub's own auto-merge behavior
    is to merge only after all required reviews and required status checks
    are

✂ Note

PR body was truncated to here.

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 •
edited
Loading

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 anyhow@1.0.100 --precise 1.0.104
error: failed to load manifest for workspace member `/tmp/renovate/repos/github/finos/morphir/crates/morphir`
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 async-trait@0.1.89 --precise 0.1.91
error: failed to load manifest for workspace member `/tmp/renovate/repos/github/finos/morphir/crates/morphir`
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-live/Cargo.toml --package js-sys@0.3.85 --precise 0.3.103
error: failed to load manifest for workspace member `/tmp/renovate/repos/github/finos/morphir/crates/morphir`
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 •
edited
Loading

Copy link
Copy Markdown

✅ Deploy Preview for angry-raman-7c44f6 canceled.

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

@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants