chore(deps): bump pest_generator from 2.8.8 to 2.9.0

[dependabot]

Bumps pest_generator from 2.8.8 to 2.9.0.

Release notes

Sourced from pest_generator's releases.

v2.9.0

What's Changed

• fix: restore stack state after a failed sequence by @​Baltsat in pest-parser/pest#1184
• fix: silence compiler and clippy warnings in tests and generator by @​NiltonVolpato in pest-parser/pest#1186
• fix(debugger): upgrade rustyline to 13 for loongarch64 support by @​tangaac in pest-parser/pest#1187
• fix(fuzz): set edition 2021 and add sql fuzz target by @​estr3llas in pest-parser/pest#1189
• Add support for a fully-functional const PrattParser with optional macro for increased ergonomics by @​NiltonVolpato in pest-parser/pest#1185
• Add fuzzing dictionaries and document them in FUZZING.md by @​estr3llas in pest-parser/pest#1191
• Reject unescaped control characters in the JSON grammar by @​hdimer in pest-parser/pest#1190

New Contributors

• @​Baltsat made their first contribution in pest-parser/pest#1184
• @​NiltonVolpato made their first contribution in pest-parser/pest#1186
• @​tangaac made their first contribution in pest-parser/pest#1187
• @​estr3llas made their first contribution in pest-parser/pest#1189
• @​hdimer made their first contribution in pest-parser/pest#1190

Full Changelog: pest-parser/pest@v2.8.8...v2.9.0

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.9", features = ["grammar-extras"] }

Commits

• d9b29b6 bump version to 2.9.0 (#1192)
• f0998ee Reject unescaped control characters in the JSON grammar (#1190)
• fa9e187 Add fuzzing dictionaries and document them in FUZZING.md (#1191)
• c3a6956 Add support for a fully-functional const PrattParser with optional macro for ...
• 6f29d56 fix(fuzz): set edition 2021 and add sql fuzz target (#1189)
• 4614db3 fix(debugger): upgrade rustyline to 13 for loongarch64 support (#1187)
• f95efcd fix: silence compiler and clippy warnings in tests and generator (#1186)
• 0f501a1 fix: restore stack state after a failed sequence (#1184)
• See full diff 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 show <dependency name> 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)

[datadoghq-integration]

More details

pest_generator and pest_meta move together to 2.9.0 while the resolved pest version remains unchanged, leaving the parser dependency graph internally consistent.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit ef9015f · @DataDog review to ask questions}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-06T16:11:50.734999Z	af13ebe	New commits
🔒 Security Review	✅ Completed 2026-10-06T16:14:49.642324Z	af13ebe	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

⚠️ Vector compatibility advisory

This check tests whether Vector can update to the VRL version in this PR without additional changes. Dependency changes can make that update significantly harder. If the required Vector changes are reasonable, you can ignore this advisory. Review the workflow run for details.