v2.6.1: pest as a git dependency #867
tomtau
announced in
Announcements
Replies: 1 comment
-
This version was yanked, you can still use the feature in 2.7.0 under a feature flag: #876
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What's Changed
New Contributors
Full Changelog: v2.6.0...v2.6.1
Using pest as a git dependency
pest v2.6.1 contains a patch for the longstanding problem that pest couldn't be used as a git dependency due to the bootstrapping process. It should be possible now with a special feature flag as follows:
Note that the compilation time will be higher due to the
cargo
library dependency. If that becomes an issue, you can still use the old workarounds, e.g. cloning the repo, runningcargo bootstrap
there and specifying the dependency as a path to the locally cloned repo instead of git.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 is a known issue and will be fixed in the future (e.g. by increasing MSRV and non_exhaustive annotations).If you face a dependency problem where Cargo mixes different versions of pest due to transitive dependencies: #849 (comment) you can try adding the older pest to explicitly force it as follows:
This discussion was created from the release v2.6.1: pest as a git dependency.
Beta Was this translation helpful? Give feedback.
All reactions