Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update rust crate nom to v8 #3411

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2025

This PR contains the following updates:

Package Type Update Change
nom dev-dependencies major 7.1.3 -> 8.0.0
nom dependencies major 7.1.3 -> 8.0.0

Release Notes

rust-bakery/nom (nom)

v8.0.0

Compare Source

This versions represents a significant refactoring of nom to reduce the amount of code generated by prsers, and reduce the API surface. As such, it comes with some breaking changes, mostly around the move from closure based combinators to trait based ones. In practice, it means that instead of writing combinator(arg)(input), we now write combinator(arg).parse(input).

This release also marks th introduction of the nom-language crate, which will hold tools more focused on language parsing than the rest of nom, like the VerboseError type and the newly added precedence parsing combinators.

Thanks
Added
  • Parser::map_res
  • Parser::map_opt
  • many and fold combinators using ranges
  • many can collect into other types than Vec
  • Error and VerboseError can be converted to owned versions
Removed
  • nom::bits::* is no longer re-exported at the crate root. This export caused frequent confusion, since e.g. nom::complete::tag referred to nom::bits::complete::tag instead of the much more commonly used nom::bytes::complete::tag. To migrate, change any imports of nom::{complete::*, streaming::*, bits, bytes} to nom::bits::[...].
  • parse combinator
  • InputIter, InputTakeAtPosition, InputLength, InputTake and Slice are now merged in the Input trait
Changed
  • Parser::map and Parser::flat_map now take a FnMut as argument

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

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

Copy link
Contributor Author

renovate bot commented Jan 27, 2025

⚠️ 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 nom@7.1.3 --precise 8.0.0
    Updating crates.io index
error: failed to select a version for the requirement `nom = "^7.1.1"`
candidate versions found which didn't match: 8.0.0
location searched: crates.io index
required by package `av1-grain v0.2.3`
    ... which satisfies dependency `av1-grain = "^0.2.3"` (locked to 0.2.3) of package `rav1e v0.7.0 (/tmp/renovate/repos/github/xiph/rav1e)`

@renovate renovate bot force-pushed the renovate/nom-8.x branch from dcabcc0 to 6239af4 Compare February 23, 2025 09:08
@renovate renovate bot force-pushed the renovate/nom-8.x branch from 6239af4 to c2df1d3 Compare February 23, 2025 12:24
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.

0 participants