Latest Results
chore(deps): bump pest_derive from 2.7.15 to 2.8.0 (#5295)
Bumps [pest_derive](https://github.com/pest-parser/pest) from 2.7.15 to
2.8.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pest-parser/pest/releases">pest_derive's
releases</a>.</em></p>
<blockquote>
<h2>v2.8.0</h2>
<h2>What's Changed</h2>
<ul>
<li>debugger: add long versions of the commands as well as all of their
prefixes by <a
href="https://github.com/alpaylan"><code>@alpaylan</code></a> in <a
href="https://redirect.github.com/pest-parser/pest/pull/1062">pest-parser/pest#1062</a></li>
<li>Debugger: Fix deadlock on Windows by <a
href="https://github.com/zaddach"><code>@zaddach</code></a> in <a
href="https://redirect.github.com/pest-parser/pest/pull/1072">pest-parser/pest#1072</a></li>
<li>Debugger: Fix command parsing on the debugger prompt by <a
href="https://github.com/zaddach"><code>@zaddach</code></a> in <a
href="https://redirect.github.com/pest-parser/pest/pull/1074">pest-parser/pest#1074</a></li>
<li>Debugger: Allow specification of several breakpoints from cmdline
args by <a href="https://github.com/zaddach"><code>@zaddach</code></a>
in <a
href="https://redirect.github.com/pest-parser/pest/pull/1075">pest-parser/pest#1075</a></li>
<li>debugger: fixed cli-parsing of id <!-- raw HTML omitted --> command
by <a
href="https://github.com/Giftzwerg02"><code>@Giftzwerg02</code></a> in
<a
href="https://redirect.github.com/pest-parser/pest/pull/1089">pest-parser/pest#1089</a></li>
<li>rm some compiler warnings by <a
href="https://github.com/yshavit"><code>@yshavit</code></a> in <a
href="https://redirect.github.com/pest-parser/pest/pull/1093">pest-parser/pest#1093</a></li>
<li>new rule: PUSH_LITERAL by <a
href="https://github.com/yshavit"><code>@yshavit</code></a> in <a
href="https://redirect.github.com/pest-parser/pest/pull/1092">pest-parser/pest#1092</a></li>
</ul>
<h3>A new rule <code>PUSH_LITERAL(...)</code>.</h3>
<p><code>PUSH_LITERAL("a")</code>: This rule always matches
and never consumes any input, and it pushes <code>"a"</code>
to the stack. The argument must be a literal.</p>
<blockquote>
<p>[!note]
You need to enable the <code>"grammar-extras"</code> feature
as mentioned in the semantic versioning notes below in order to use this
feature.</p>
</blockquote>
<p>This new rule accomplishes the goals of <a
href="https://redirect.github.com/pest-parser/pest/issues/880">pest-parser/pest#880</a>
(in a slightly different way). Instead of
<code>PUSH_OTHER("-", " ")</code>, this is just
<code>PUSH_LITERAL(" ")</code>. If you wanted to match A and
then push B, you just combine them via a sequence: <code>"-" ~
PUSH_LITERAL(" ")</code>.</p>
<p>This can be used to generalize quoted strings to a pair of matching
but non-equal delimiters. For example, many programming languages let
you express strings using either double or single quotes, and don't
require escaping of the other:</p>
<pre><code>string = ${ PUSH( "\"" | "'") ~
quoted_char* ~ POP }
quoted_char = @{!PEEK ~ ANY } // simple version without escape sequences
<p>// will parse "a'b" or 'a"b'
</code></pre></p>
<p>This happens to work because the starting and ending char are the
same, but that's not always desirable. For example, we may want to allow
strings to be delimited by either <code>(</code> ... <code>)</code> or
<code><</code> ... <code>></code>, with similar rules as above,
such that <code>(a>)</code> and <code><a)></code> are both
valid.</p>
<p>With <code>PUSH_LITERAL</code>, this becomes:</p>
<pre><code>string = ${ quote_open ~ quoted_char* ~ POP }
quote_open = @{
( "(" ~ PUSH_LITERAL(")") )
| ( "<" ~ PUSH_LITERAL(">") )
}
quoted_char = @{!PEEK ~ ANY } // simple version without escape sequences
</code></pre>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/alpaylan"><code>@alpaylan</code></a>
made their first contribution in <a
href="https://redirect.github.com/pest-parser/pest/pull/1062">pest-parser/pest#1062</a></li>
<li><a href="https://github.com/zaddach"><code>@zaddach</code></a> made
their first contribution in <a
href="https://redirect.github.com/pest-parser/pest/pull/1072">pest-parser/pest#1072</a></li>
<li><a
href="https://github.com/Giftzwerg02"><code>@Giftzwerg02</code></a>
made their first contribution in <a
href="https://redirect.github.com/pest-parser/pest/pull/1089">pest-parser/pest#1089</a></li>
<li><a href="https://github.com/yshavit"><code>@yshavit</code></a> made
their first contribution in <a
href="https://redirect.github.com/pest-parser/pest/pull/1093">pest-parser/pest#1093</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a
href="https://github.com/pest-parser/pest/compare/v2.7.15...v2.8.0">https://github.com/pest-parser/pest/compare/v2.7.15...v2.8.0</a></p>
<h2>Warning: Semantic Versioning</h2>
<p>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 <code>Rule</code> enum.</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pest-parser/pest/commit/111e7793a7522bbda71f84c20b70254e050b641f"><code>111e779</code></a>
bump version to 2.8.0 (<a
href="https://redirect.github.com/pest-parser/pest/issues/1094">#1094</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/2b30b8d16008125ead7d1d5af7b7a53a7bc1a64f"><code>2b30b8d</code></a>
new rule: PUSH_LITERAL (<a
href="https://redirect.github.com/pest-parser/pest/issues/1092">#1092</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/61f1ebcf32c4894abcdda835476798bf3cd989d7"><code>61f1ebc</code></a>
rm some compiler warnings (<a
href="https://redirect.github.com/pest-parser/pest/issues/1093">#1093</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/17a7fa0b04d9aaf7f4bf43f5f57a701186df1ed4"><code>17a7fa0</code></a>
fixed cli-parsing of id <text-input> command (<a
href="https://redirect.github.com/pest-parser/pest/issues/1089">#1089</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/7a809dd9c7826cca9d572879885bf5b59fcbe890"><code>7a809dd</code></a>
bump toolchain in semver check (<a
href="https://redirect.github.com/pest-parser/pest/issues/1091">#1091</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/b1869d52525e812e1c07109a5d8452847fb8a04f"><code>b1869d5</code></a>
bump toolchain (<a
href="https://redirect.github.com/pest-parser/pest/issues/1090">#1090</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/a13c05c77840420946ca1fbfd1890d2b5f0b93b2"><code>a13c05c</code></a>
check if a crate version was already published (<a
href="https://redirect.github.com/pest-parser/pest/issues/1078">#1078</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/eca1f1c61d8a91cefb82e18edd087a0f042a4f46"><code>eca1f1c</code></a>
Debugger: Allow specification of several breakpoints from cmdline args
(<a
href="https://redirect.github.com/pest-parser/pest/issues/1075">#1075</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/f2f431060c536da0cfa9d386af06a79ae04c5f46"><code>f2f4310</code></a>
fix CIFuzz action (<a
href="https://redirect.github.com/pest-parser/pest/issues/1077">#1077</a>)</li>
<li><a
href="https://github.com/pest-parser/pest/commit/8ea0c31c0e3086e4425301ddb51f7e47d20ba8ef"><code>8ea0c31</code></a>
Debugger: Fix command parsing on the debugger prompt (<a
href="https://redirect.github.com/pest-parser/pest/issues/1074">#1074</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/pest-parser/pest/compare/v2.7.15...v2.8.0">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
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 <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)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Active Branches
#53020%
#52490%
#52280%
© 2025 CodSpeed Technology