dependabot[bot] opened a new pull request, #41952: URL: https://github.com/apache/superset/pull/41952
Bumps [syntaqlite](https://github.com/LalitMaganti/syntaqlite) from 0.4.2 to 0.6.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/LalitMaganti/syntaqlite/releases";>syntaqlite's releases</a>.</em></p> <blockquote> <h2>v0.6.0</h2> <p><strong>Shell file support:</strong></p> <ul> <li>syntaqlite now understands SQLite shell scripts: files that mix <code>.dot</code> commands with SQL. The embedded SQL is extracted and the surrounding shell syntax is ignored, so <code>ast</code>, <code>fmt</code>, and <code>validate</code> all operate on just the SQL regions (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/275";>#275</a>, <a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/276";>#276</a>).</li> <li>The LSP analyzes embedded SQL the same way, surfacing diagnostics on the SQL inside shell files directly in your editor (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/276";>#276</a>).</li> </ul> <p><strong>Python / Pyodide:</strong></p> <ul> <li>syntaqlite can now run in the browser and other Pyodide environments via a Pyodide wheel (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/272";>#272</a>).</li> <li>The Python bindings now run the parser in-process instead of shelling out to a subprocess (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/271";>#271</a>).</li> </ul> <p><strong>Performance:</strong></p> <ul> <li>Amalgamated builds are faster: dialect virtual functions are now inlined automatically (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/266";>#266</a>).</li> </ul> <h2>v0.5.10</h2> <p><strong>Zed extension:</strong></p> <ul> <li>Renamed the extension and its language server id to <code>syntaqlite-lsp</code> and bundled a license, retooling it to meet the Zed extension registry's requirements (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/267";>#267</a>).</li> </ul> <h2>v0.5.9</h2> <p><strong>Parser:</strong></p> <ul> <li>Reverted the eager macro argument expansion introduced in 0.5.8, which broke the rewrite tree shape expected by downstream consumers. The diamond-recursion case it fixed is now detected structurally by walking the expansion layer's parent chain through <code>body_call_offset == ARG_INTERNAL</code> links, with no pre-expansion needed (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/262";>#262</a>).</li> </ul> <h2>v0.5.8</h2> <p><strong>Parser:</strong></p> <ul> <li>Macro arguments are now eagerly expanded at the call site before the body is instantiated. This fixes the "diamond" macro problem where an inner macro appeared to recurse through a parent even though no real cycle existed, and also speeds up macros that reference the same argument multiple times (the argument is expanded once instead of N times) (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/260";>#260</a>).</li> </ul> <h2>v0.5.7</h2> <p><strong>Build:</strong></p> <ul> <li>Linux CLI binaries (<code>syntaqlite-linux-x64.tar.gz</code>, <code>syntaqlite-linux-arm64.tar.gz</code>) are now built inside <code>manylinux_2_28</code> containers, pinning them to glibc 2.28 (RHEL 8 / Ubuntu 20.04+ / Debian 10+) instead of inheriting <code>ubuntu-latest</code>'s glibc 2.39. Fixes <code>GLIBC_2.39 not found</code> when running the prebuilt CLI on older Linux hosts (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/258";>#258</a>).</li> <li>Added a Nix flake for building and running the CLI: <code>nix build</code>, <code>nix run</code>, and consumption via <code>overlays.default</code> are all supported (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/253";>#253</a>).</li> </ul> <h2>v0.5.6</h2> <p><strong>Rust API:</strong></p> <ul> <li>Added <code>AnyParsedStatement::node_token_range(node_id)</code> returning the inclusive token range for any AST node. Ranges include expansion-layer tokens, so macro-produced nodes report meaningful ranges instead of collapsing to empty (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li>Added <code>AnyParsedStatement::node_leading_comments</code> / <code>node_trailing_comments</code> as composition sugar over <code>node_token_range</code> + <code>token_{leading,trailing}_comments</code> for the common boundary-comment case (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li>Token API is now layer-aware: offsets/lengths are typed as <code>LayerOffset</code> / <code>LayerLen</code>, <code>text()</code> resolves per-layer, and <code>stmt_range()</code> drills expansion tokens up to the authored call site in source coordinates. <code>layer_id()</code> is exposed on tokens (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/247";>#247</a>).</li> <li><code>Comment::layer_id</code> distinguishes authored-source comments (layer 0) from comments inside macro expansion bodies (layer > 0); <code>Comment::text()</code> resolves against the owning layer's buffer (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li>Removed <code>AnyParsedStatement::token_spans()</code> — use <code>tokens().map(|t| t.stmt_range())</code> instead (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/247";>#247</a>).</li> </ul> <p><strong>C API:</strong></p> <ul> <li>Added <code>syntaqlite_node_token_range(p, node_id, &first, &last)</code> for O(1) inclusive token ranges per AST node, and <code>syntaqlite_node_{leading,trailing}_comments</code> for boundary comments at the node level (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li><code>SyntaqliteComment.layer_id</code> now distinguishes authored-source comments from comments inside macro expansion bodies (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> </ul> <p><strong>Formatter:</strong></p> <ul> <li>New block-comment classification rule: a block comment is trailing on the preceding token only if it is same-line with that token AND nothing else follows on the rest of the line; otherwise it is leading on the next token. Line comments are unchanged (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li>Fixed <code>/* c */ KEYWORD</code> losing its separator between the comment and the following keyword after the leading-comment drain cleared <code>pending</code> (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> </ul> <h2>v0.5.5</h2> <p><strong>C API:</strong></p> <ul> <li>Public-API offsets and lengths are now typed with named aliases: <code>SyntaqliteDocOffset</code> / <code>SyntaqliteStmtOffset</code> / <code>SyntaqliteLayerOffset</code> make the coordinate system explicit, and <code>SyntaqliteLength</code> replaces the parallel <code>*Len</code> aliases. <code>SyntaqliteDiagnostic</code> offsets are now documented as document-absolute even when read via <code>statement_diagnostics</code> (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/244";>#244</a>).</li> </ul> <p><strong>Build:</strong></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/LalitMaganti/syntaqlite/blob/main/CHANGELOG.md";>syntaqlite's changelog</a>.</em></p> <blockquote> <h2>0.6.0</h2> <p><strong>Shell file support:</strong></p> <ul> <li>syntaqlite now understands SQLite shell scripts — files that mix <code>.dot</code> commands with SQL. The embedded SQL is extracted and the surrounding shell syntax is ignored, so <code>ast</code>, <code>fmt</code>, and <code>validate</code> all operate on just the SQL regions (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/275";>#275</a>, <a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/276";>#276</a>).</li> <li>The LSP analyzes embedded SQL the same way, surfacing diagnostics on the SQL inside shell files directly in your editor (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/276";>#276</a>).</li> </ul> <p><strong>Python / Pyodide:</strong></p> <ul> <li>syntaqlite can now run in the browser and other Pyodide environments via a Pyodide wheel (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/272";>#272</a>).</li> <li>The Python bindings now run the parser in-process instead of shelling out to a subprocess (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/271";>#271</a>).</li> </ul> <p><strong>Performance:</strong></p> <ul> <li>Amalgamated builds are faster — dialect virtual functions are now inlined automatically (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/266";>#266</a>).</li> </ul> <h2>0.5.10</h2> <p><strong>Zed extension:</strong></p> <ul> <li>Renamed the extension and its language server id to <code>syntaqlite-lsp</code> and bundled a license, retooling it to meet the Zed extension registry's requirements (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/267";>#267</a>).</li> </ul> <h2>0.5.9</h2> <p><strong>Parser:</strong></p> <ul> <li>Reverted the eager macro argument expansion introduced in 0.5.8, which broke the rewrite tree shape expected by downstream consumers. The diamond-recursion case it fixed is now detected structurally by walking the expansion layer's parent chain through <code>body_call_offset == ARG_INTERNAL</code> links, with no pre-expansion needed (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/262";>#262</a>).</li> </ul> <h2>0.5.8</h2> <p><strong>Parser:</strong></p> <ul> <li>Macro arguments are now eagerly expanded at the call site before the body is instantiated. This fixes the "diamond" macro problem where an inner macro appeared to recurse through a parent even though no real cycle existed, and also speeds up macros that reference the same argument multiple times (the argument is expanded once instead of N times) (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/260";>#260</a>).</li> </ul> <h2>0.5.7</h2> <p><strong>Build:</strong></p> <ul> <li>Linux CLI binaries (<code>syntaqlite-linux-x64.tar.gz</code>, <code>syntaqlite-linux-arm64.tar.gz</code>) are now built inside <code>manylinux_2_28</code> containers, pinning them to glibc 2.28 (RHEL 8 / Ubuntu 20.04+ / Debian 10+) instead of inheriting <code>ubuntu-latest</code>'s glibc 2.39. Fixes <code>GLIBC_2.39 not found</code> when running the prebuilt CLI on older Linux hosts (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/258";>#258</a>).</li> <li>Added a Nix flake for building and running the CLI: <code>nix build</code>, <code>nix run</code>, and consumption via <code>overlays.default</code> are all supported (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/253";>#253</a>).</li> </ul> <h2>0.5.6</h2> <p><strong>Rust API:</strong></p> <ul> <li>Added <code>AnyParsedStatement::node_token_range(node_id)</code> returning the inclusive token range for any AST node. Ranges include expansion-layer tokens, so macro-produced nodes report meaningful ranges instead of collapsing to empty (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li>Added <code>AnyParsedStatement::node_leading_comments</code> / <code>node_trailing_comments</code> as composition sugar over <code>node_token_range</code> + <code>token_{leading,trailing}_comments</code> for the common boundary-comment case (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li>Token API is now layer-aware: offsets/lengths are typed as <code>LayerOffset</code> / <code>LayerLen</code>, <code>text()</code> resolves per-layer, and <code>stmt_range()</code> drills expansion tokens up to the authored call site in source coordinates. <code>layer_id()</code> is exposed on tokens (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/247";>#247</a>).</li> <li><code>Comment::layer_id</code> distinguishes authored-source comments (layer 0) from comments inside macro expansion bodies (layer > 0); <code>Comment::text()</code> resolves against the owning layer's buffer (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li>Removed <code>AnyParsedStatement::token_spans()</code> — use <code>tokens().map(|t| t.stmt_range())</code> instead (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/247";>#247</a>).</li> </ul> <p><strong>C API:</strong></p> <ul> <li>Added <code>syntaqlite_node_token_range(p, node_id, &first, &last)</code> for O(1) inclusive token ranges per AST node, and <code>syntaqlite_node_{leading,trailing}_comments</code> for boundary comments at the node level (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li><code>SyntaqliteComment.layer_id</code> now distinguishes authored-source comments from comments inside macro expansion bodies (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> </ul> <p><strong>Formatter:</strong></p> <ul> <li>New block-comment classification rule: a block comment is trailing on the preceding token only if it is same-line with that token AND nothing else follows on the rest of the line; otherwise it is leading on the next token. Previously, any block comment same-line with the preceding token was treated as trailing, conflating "annotates the prev token" with "sits between two tokens". Line comments are unchanged (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> <li>Fixed <code>/* c */ KEYWORD</code> losing its separator between the comment and the following keyword after the leading-comment drain cleared <code>pending</code> (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/pull/248";>#248</a>).</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/b6e3d42381dbf6e6ea4cad0aa9193b2c435499b0";><code>b6e3d42</code></a> synq: bump version to 0.6.0 (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/279";>#279</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/d3d408e16c92272870c25e4f7cefed72bec9809d";><code>d3d408e</code></a> synq: add docs about our support for handling SQLite shell files (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/277";>#277</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/cd501d4b53c5f74eeb164698d238fcc354bb1394";><code>cd501d4</code></a> synq: analyze embedded SQL in the LSP via masking</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/82f3eb6b973887c51367ec7b0a6cf07604591bc1";><code>82f3eb6</code></a> synq: handle embedded SQL across all CLI commands (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/276";>#276</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/cf78ccf55e738e0ac6ddc990dd6016b1331a55dd";><code>cf78ccf</code></a> synq: add embedded SQL extraction engine with shell support (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/275";>#275</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/649328a19d90a89b2c87242b789447efc657d782";><code>649328a</code></a> synq: resolve all-underscore identifiers as SQL placeholders (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/274";>#274</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/503e4942f321616b24447e8138b10dbaad5204d9";><code>503e494</code></a> synq: add support for buidling for pyiodide (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/272";>#272</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/627ddc5c0c188afe0082d488d0efbd47768a6f0e";><code>627ddc5</code></a> synq: add in-process FFI transport for Python bindings (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/271";>#271</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/4219527e8784dece57f8280af7320f2adb454f05";><code>4219527</code></a> synq: automatically inline dialect virtual functions in amalgamations (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/266";>#266</a>)</li> <li><a href="https://github.com/LalitMaganti/syntaqlite/commit/2ba2eecd190de74c7e4ddd2cf70898c071b79b52";><code>2ba2eec</code></a> synq: fix symbol export in syntaqlite CLI for dynamically loaded dialects (<a href="https://redirect.github.com/LalitMaganti/syntaqlite/issues/264";>#264</a>)</li> <li>Additional commits viewable in <a href="https://github.com/LalitMaganti/syntaqlite/compare/v0.4.2...v0.6.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 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> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
