Skip to content

chore(deps): update cargo non-major dependencies#67

Draft
dd-octo-sts[bot] wants to merge 1 commit intomainfrom
engraver-auto-version-upgrade/renovate/cargo-non-major-dependencies
Draft

chore(deps): update cargo non-major dependencies#67
dd-octo-sts[bot] wants to merge 1 commit intomainfrom
engraver-auto-version-upgrade/renovate/cargo-non-major-dependencies

Conversation

@dd-octo-sts
Copy link
Copy Markdown

@dd-octo-sts dd-octo-sts bot commented Mar 6, 2026

This PR contains the following updates:

Package Type Update Change
anyhow dependencies patch 1.0.1001.0.102
chrono dependencies patch 0.4.430.4.44
clap dependencies patch 4.5.564.5.60
pbjson-types dependencies minor 0.8.00.9.0
pest (source) dependencies patch 2.8.52.8.6
pest_derive (source) dependencies patch 2.8.52.8.6

Release Notes

dtolnay/anyhow (anyhow)

v1.0.102

Compare Source

v1.0.101

Compare Source

chronotope/chrono (chrono)

v0.4.44: 0.4.44

Compare Source

What's Changed

clap-rs/clap (clap)

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

v4.5.57

Compare Source

Fixes
  • Regression from 4.5.55 where having an argument with .value_terminator("--") caused problems with an argument with .last(true)
pest-parser/pest (pest)

v2.8.6

Compare Source

What's Changed
New Contributors

Full Changelog: pest-parser/pest@v2.8.5...v2.8.6

Warning: Semantic Versioning

Note that the node tag feature in 2.6.0 was a technically semver-breaking change even though it is a backwards-compatible / non-breaking change in the meta-grammar. There may be similar non-breaking changes to the meta-grammar between minor versions in the future. These non-breaking changes, however, may translate into semver-breaking changes due to the additional variants propagated from the generated Rule enum.

This new feature caused issues in some Cargo version resolution situations where Cargo mixed different versions of pest dependencies. For this reason, these "grammar non-breaking but semver-breaking" changes are now available only under the "grammar-extras" feature flag. If you would like to use node tags (or other future grammar features), you can do so by enabling this flag on the pest_derive crate in your Cargo.toml:

...
pest_derive = { version = "2.8", features = ["grammar-extras"] }

Configuration

📅 Schedule: 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 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.


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

This PR has been generated by Renovate Bot.

@dd-octo-sts
Copy link
Copy Markdown
Author

dd-octo-sts bot commented Mar 6, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact 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.102
error: rustup could not choose a version of cargo to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants