chore(deps): update rust - #638
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
✅ Deploy Preview for angry-raman-7c44f6 canceled.
|
renovate
Bot
force-pushed
the
renovate/rust
branch
from
April 2, 2026 19:35
ed8dab3 to
96b1eb6
Compare
renovate
Bot
force-pushed
the
renovate/rust
branch
from
April 28, 2026 05:13
96b1eb6 to
2bbae09
Compare
renovate
Bot
force-pushed
the
renovate/rust
branch
3 times, most recently
from
June 23, 2026 01:07
9ac1a70 to
7445797
Compare
renovate
Bot
force-pushed
the
renovate/rust
branch
2 times, most recently
from
July 8, 2026 04:45
784aef0 to
2bc11d5
Compare
renovate
Bot
force-pushed
the
renovate/rust
branch
from
July 10, 2026 10:57
2bc11d5 to
1762af9
Compare
renovate
Bot
force-pushed
the
renovate/rust
branch
from
July 27, 2026 14:29
1762af9 to
bd9237d
Compare
renovate
Bot
force-pushed
the
renovate/rust
branch
3 times, most recently
from
August 17, 2026 10:00
04eb66d to
788151d
Compare
2 tasks
renovate
Bot
force-pushed
the
renovate/rust
branch
5 times, most recently
from
August 17, 2026 20:57
ac3e535 to
0a94f83
Compare
renovate
Bot
force-pushed
the
renovate/rust
branch
6 times, most recently
from
August 24, 2026 00:31
2cc1ddd to
699c82e
Compare
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
Bot
force-pushed
the
renovate/rust
branch
29 times, most recently
from
August 29, 2026 04:48
cd712b2 to
9e43d15
Compare
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:
0.22→0.230.22→0.232.14.0→2.14.14.3.0→4.4.01.1.0→1.2.06.1.1→6.6.0Release Notes
cucumber-rs/cucumber (cucumber)
v0.23.0Compare Source
Diff | Milestone
BC Breaks
Changed
gherkin] crate to 0.16 version. (0d544772)And-like andBut-like keywords at the beginning ofScenario, automatically considering them asGiven-type steps. (gherkin#53)indexmap-rs/indexmap (indexmap)
v2.14.1Compare Source
Equivalentisn't needed (Q = K).expect) clippy lints.owo-colors/owo-colors (owo-colors)
v4.4.0Compare Source
Changed
bourumir-wyngs/serde-saphyr (serde-saphyr)
v1.2.0Compare Source
Changed
Budget; property resource-limitfailures are now reported through
Error::BudgetandBudgetBreach.Options::reject_unsupported_tagsstrict mode. It rejects explicitly taggedscalar, 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
!!mergeand!!valueareaccepted in this mode only as the exact scalar mapping keys
<<and=, respectively, whilerobotics-only
!degreesand!radiansrequire both theroboticscrate feature andangle_conversions, and!includerequires both theincludecrate feature and a configuredresolver.
reject_unsupported_tagsis disabled.indent_stepis now limited to1..=64, allserializer 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.
contain whitespace, control characters, or YAML flow punctuation; unsupported names now return
a serialization error.
Fixes
!!mergekeys, including verbatim tags and%TAG-expandedhandles, everywhere implicit
<<merge keys are supported.!!valuetag while intentionally treating it as a no-op annotation.#-prefixed content lines.typetagtrait-object deserialization by consuming the closing mappingevent when a Serde map visitor returns after its final key/value pair, preventing a false
"multiple YAML documents" error.
identity handling, preventing lossy path collisions and policy bypasses on Unix.
while retaining the anchor-definition locations as secondary context.
Testing
we use YAML Test Suite v2022-01-17.
jdx/usage (usage-lib)
v6.6.0Compare Source
🚀 Features
v6.5.0Compare Source
🚀 Features
🐛 Bug Fixes
New Contributors
v6.4.1Compare Source
🐛 Bug Fixes
🔍 Other Changes
📦️ Dependency Updates
v6.4.0Compare Source
🚀 Features
🐛 Bug Fixes
🚜 Refactor
v6.3.0Compare Source
🚀 Features
🐛 Bug Fixes
v6.2.0Compare Source
🚀 Features
🐛 Bug Fixes
🚜 Refactor
⚡ Performance
🛡️ Security
🔍 Other Changes
str downcasethingy in nushell by @TheBearodactyl in #1262New Contributors
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.