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

Outdated transitive nom dependencies #95

Closed
nashley opened this issue Apr 17, 2023 · 3 comments
Closed

Outdated transitive nom dependencies #95

nashley opened this issue Apr 17, 2023 · 3 comments
Milestone

Comments

@nashley
Copy link

nashley commented Apr 17, 2023

  Downloaded hwatch v0.3.10
...
    Finished release [optimized] target(s) in 1m 23s
warning: the following packages contain code that will be rejected by a future version of Rust: nom v4.2.3, nom v5.1.2
note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`

cargo tree shows the outdated nom dependencies coming from ansi-parser v0.8.0 and termwiz v0.15.0's terminfo v0.7.3 respectively:

hwatch v0.3.10 (/home/user/git/hwatch)
├── ansi-parser v0.8.0
...
│   └── nom v4.2.3
...
└── termwiz v0.15.0
...
    ├── terminfo v0.7.3
    │   ├── nom v5.1.2
...

ansi-parser doesn't seem to have an updated version available, but termwiz does (and it uses an updated terminfo that uses nom 7)

@blacknon
Copy link
Owner

Wow, Thanks!
I will update it in the next version.

@blacknon blacknon added this to the 0.3.11 milestone Apr 17, 2023
@nashley
Copy link
Author

nashley commented Apr 17, 2023

Actually it looks like termwiz has only published 0.20 and not 0.22, which includes the bump of terminfo from 0.7 to 0.8, which is needed for the nom version bump. Hopefully they will soon.

@blacknon blacknon modified the milestones: 0.3.12, 0.3.13 Apr 7, 2024
@blacknon blacknon mentioned this issue May 6, 2024
blacknon added a commit that referenced this issue May 6, 2024
@blacknon
Copy link
Owner

blacknon commented May 6, 2024

The issue was resolved by applying version 0.9.0 of ansi-parser.
This issue will be closed. Thank you for the issue.

@blacknon blacknon closed this as completed May 6, 2024
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

No branches or pull requests

2 participants