You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say that the crate has a breaking change and updates to 0.10, but you forget to change README.md to reflect this. It'd be nice if skeptic could somehow fail and indicate to the user that README.md should be updated to reflect the latest version.
I've had a few crates stumble upon this mistake (including several of my own) and it'd be nice if skeptic could keep track of this too!
The text was updated successfully, but these errors were encountered:
This should be doable in a basic form as we started to use cargo_metadata to solve some more tricky linkage scenarios.
At the moment I don't think it would be possible to (easily) match against features or dependencies other than crates.io ones (path/vcs), but a basic form that would check if cargo.toml snippet is semver compat with build deps would be possible. Would it be enough @clarcharr ?
For example, this crate itself has the block:
Let's say that the crate has a breaking change and updates to 0.10, but you forget to change
README.md
to reflect this. It'd be nice ifskeptic
could somehow fail and indicate to the user thatREADME.md
should be updated to reflect the latest version.I've had a few crates stumble upon this mistake (including several of my own) and it'd be nice if
skeptic
could keep track of this too!The text was updated successfully, but these errors were encountered: