Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.20.0
->0.20.2
0.20.0
->0.20.2
2.7.9
->2.7.10
1.0.116
->1.0.117
0.6.7
->0.6.9
Release Notes
lalrpop/lalrpop (lalrpop)
v0.20.2
Compare Source
Special thanks to our newest maintainers, Daniel Burgener and Patrick LaFontaine for helping to coordinate this release.
Features
is-terminal
crate (thanks to Kmeakin!)regex-automata
crate (thanks to QuarticCat!)_
case for token matching can now be set to a higher precedence in match (thanks to fpoli!)Bugfixes
for the report!)
lalrpop's defaults
Compatibility note
1.70
.process_root_unconditionally
now correctly lints as having been deprecated.__
and should not be relied upon are no longer publicly exposed (thanks to arnaudgolfouse!)v0.20.1
Compare Source
Yanked
pest-parser/pest (pest)
v2.7.10
Compare Source
What's Changed
There was a performance regression in 2.7.9 due to the overhead from tracking for better error details. This is now disabled by default, but if you wish to use it, you can enable it via the
pest::set_error_detail(true)
call (before your parsing code starts).Full Changelog: pest-parser/pest@v2.7.9...v2.7.10
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:
serde-rs/json (serde_json)
v1.0.117
Compare Source
winnow-rs/winnow (winnow)
v0.6.9
Compare Source
Compatibility
Features
Debug
impls forstream::Stateful
andstream::Recoverable
v0.6.8
Compare Source
Features
&mut [impl Parser]
withinalt
Configuration
📅 Schedule: Branch creation - "before 5am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.