build(deps): bump pest_derive from 2.7.6 to 2.7.11

[dependabot[bot]]

Bumps pest_derive from 2.7.6 to 2.7.11.

Release notes

Sourced from pest_derive's releases.

v2.7.11

What's Changed

• Avoid computing line offsets after the last token by @​wabain in pest-parser/pest#1023
• fix: Remove unnecessary qualification by @​austriancoder in pest-parser/pest#1024

New Contributors

• @​wabain made their first contribution in pest-parser/pest#1023
• @​austriancoder made their first contribution in pest-parser/pest#1024

Full Changelog: https://github.com/pest-parser/pest/compare/v2.7.10...v2.7.11

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:

...
pest_derive = { version = "2.7", features = ["grammar-extras"] }

v2.7.10

What's Changed

• make tracking for better error details optional (fixes #1009) by @​tomtau in pest-parser/pest#1013

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: https://github.com/pest-parser/pest/compare/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:

...
pest_derive = { version = "2.7", features = ["grammar-extras"] }

v2.7.9

What's Changed

• fix: do not generate empty docstring for Rule by @​sunng87 in pest-parser/pest#987
• feat: support better error reporting by @​EmirVildanov in pest-parser/pest#965
• Remove unnecessary unsafe functions by @​djkoloski in pest-parser/pest#998

New Contributors

• @​djkoloski made their first contribution in pest-parser/pest#998

Full Changelog: https://github.com/pest-parser/pest/compare/v2.7.8...v2.7.9

Warning: Semantic Versioning

... (truncated)

Commits

• 21287a9 bump version to 2.7.11
• 34792f8 fix: Remove unnecessary qualification (#1024)
• b858b4a do not compute line offsets after the last token (#1023)
• f090ec1 make tracking for better error details optional (fixes #1009) (#1013)
• f60b518 bump version to 2.7.9 (#1002)
• 9d25248 Remove unnecessary unsafe functions (#998)
• 9f9094e feat: support additional parsing error information (rule call stacks and (un)...
• 30c7094 fix: do not generate empty docstring for Rule (#987)
• 28c01cb fix: adjust tag association in optional and repeat expressions (#985)
• 57daac4 feat: add sql grammar with pratt parser and tests (#983)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #839.