dependabot[bot] opened a new pull request, #4909: URL: https://github.com/apache/arrow-adbc/pull/4909
Bumps [modernc.org/sqlite](https://gitlab.com/cznic/sqlite) from 1.59.0 to 1.60.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://gitlab.com/cznic/sqlite/blob/master/CHANGELOG.md";>modernc.org/sqlite's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>Entries for v1.38.1 through v1.44.1 and for v1.49.1 were added on 2026-09-05, reconstructed from the git history and the merge requests they cite; they were missing at release time.</p> <ul> <li> <p>2026-09-30 v1.61.0:</p> <ul> <li>Add <code>_time_format=string_no_monotonic</code>, <strong>opt-in</strong>: times are written in the default layout but without Go's monotonic clock reading, the <code> m=+...</code> suffix, so a scanned time matches its row again when bound in <code>WHERE col = ?</code>. The default is unchanged. Resolves [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/259";>#259</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/259";>https://gitlab.com/cznic/sqlite/-/issues/259</a>). See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/142";>#142</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/142";>https://gitlab.com/cznic/sqlite/-/merge_requests/142</a>), thanks 不插电 (<a href="https://gitlab.com/r27153733";><code>@r27153733</code></a>)!</li> <li>Each release tag now gets a signed provenance document, linked from its GitLab release; <code>VERIFYING.md</code> says what it proves and how to check one. Tooling only. See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/141";>#141</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/141";>https://gitlab.com/cznic/sqlite/-/merge_requests/141</a>).</li> <li>Add an opt-in SQLite authorizer per connection: <code>AuthorizerRegisterer</code>, reached through <code>sql.Conn.Raw</code> or installed on every pooled connection from <code>RegisterConnectionHook</code>; existing connections are unchanged. Resolves [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/256";>#256</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/256";>https://gitlab.com/cznic/sqlite/-/issues/256</a>). See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/139";>#139</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/139";>https://gitlab.com/cznic/sqlite/-/merge_requests/139</a>), thanks Tedla Brandsema (<a href="https://gitlab.com/TedlaBrandsema";><code>@TedlaBrandsema</code></a>)!</li> <li>Closing a connection now forgets the pre-update, commit and rollback hooks registered on it; their entries used to linger after <code>Close</code>.</li> <li><strong>With a shared cache, <code>BeginTx</code> now waits for a lock another connection holds</strong> instead of failing at once with <code>SQLITE_LOCKED_SHAREDCACHE</code> (262), as executing <code>BEGIN IMMEDIATE</code> did; <code>Commit</code> and <code>Rollback</code> wait likewise while another connection changes the schema. <code>busy_timeout</code> does not bound the wait; the call's context does. See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/143";>#143</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/143";>https://gitlab.com/cznic/sqlite/-/merge_requests/143</a>), thanks Ian Chechin!</li> <li><code>PrepareContext</code> and <code>BeginTx</code> with a context that is already done now return the context's error, as <code>ExecContext</code> and <code>QueryContext</code> do. See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/143";>#143</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/143";>https://gitlab.com/cznic/sqlite/-/merge_requests/143</a>), thanks Ian Chechin!</li> </ul> </li> <li> <p>2026-09-29 v1.60.1:</p> <ul> <li>Binding arguments to a statement is no longer quadratic in the number of its parameters, which made multi-row <code>INSERT</code>s with thousands of <code>?</code> parameters slow. Resolves [GitHub issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/8";>#8</a>](<a href="https://redirect.github.com/modernc-org/sqlite/issues/8";>modernc-org/sqlite#8</a>), thanks wencycool!</li> </ul> </li> <li> <p>2026-09-28 v1.60.0:</p> <ul> <li><strong>A fault while reading the memory-mapped <code>-shm</code> file of a WAL database no longer crashes the process.</strong> The statement fails with a disk I/O error, extended code <code>SQLITE_IOERR_IN_PAGE</code> (8714), and the connection stays usable, as in MSVC builds of SQLite. On by default on every platform and not switchable; <code>lib.SehInject</code> and <code>lib.SehPending</code> inject such a fault for tests. Resolves [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/221";>#221</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/221";>https://gitlab.com/cznic/sqlite/-/issues/221</a>), thanks Roman (<a href="https://gitlab.com/requilence";><code>@requilence</code></a>) for the report, and supersedes <a href="https://gitlab.com/cznic/libsqlite3/-/merge_requests/4";>libsqlite3!4</a> and [GitHub pull request <a href="https://gitlab.com/cznic/sqlite/-/work_items/7";>#7</a>](<a href="https://redirect.github.com/modernc-org/sqlite/pull/7";>modernc -org/sqlite#7</a>), thanks hazyhaar for the two rounds, the <code>ccgo</code> finding and the Windows Server runs!</li> <li>Re-vendor <code>lib/</code> from <a href="https://gitlab.com/cznic/libsqlite3/-/tags/v1.15.0";>modernc.org/libsqlite3 v1.15.0</a> and <code>vec/</code> from <a href="https://gitlab.com/cznic/libsqlite_vec/-/tags/v0.6.0";>modernc.org/libsqlite_vec v0.6.0</a>; SQLite stays 3.53.4 and sqlite-vec v0.1.9. <strong>Go 1.26 is now required</strong>, and the pinned <code>modernc.org/libc</code> becomes <a href="https://gitlab.com/cznic/libc/-/tags/v1.77.1";>v1.77.1</a>; as always, downstream <code>go.mod</code> files must pin the same <code>modernc.org/libc</code> version this repository's <code>go.mod</code> does, see [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/177";>#177</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/177";>https://gitlab.com/cznic/sqlite/-/issues/177</a>).</li> <li><strong>Nine exported <code>lib</code> constants that never had a meaningful value are gone</strong>: <code>INFINITY</code>, <code>MB_CUR_MAX</code>, <code>NAN</code>, <code>RESERVED_BYTE</code>, <code>SHARED_FIRST</code>, <code>SQLITE_CANTOPEN_BKPT</code>, <code>SQLITE_CORRUPT_BKPT</code>, <code>SQLITE_DEFAULT_LOOKASIDE</code> and <code>SQLITE_MISUSE_BKPT</code>. The transpiler now evaluates object-like macros as C expressions, so other constants take their C value (<code>lib.WALINDEX_PGSZ</code> is 32768, not 0) and some appear; the full list is in <a href="https://gitlab.com/cznic/libsqlite3/-/blob/master/CHANGELOG.md";>libsqlite3's CHANGELOG</a> under 2026-09-19.</li> <li><code>make vendor</code> now writes <code>vendor.json</code>, the <code>modernc.org/libsqlite3</code> and <code>modernc.org/libsqlite_vec</code> commits and the Go toolchain <code>lib/</code> and <code>vec/</code> were vendored with, so <code>git show vX.Y.Z:vendor.json</code> says which revisions a release carries; the test suite fails when they no longer match. Tooling only. See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/140";>#140</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/140";>https://gitlab.com/cznic/sqlite/-/merge_requests/140</a>).</li> <li><strong><code>vfs.FS.Close</code> now refuses while a database opened through it is still open</strong>, returning an error that wraps the new <code>vfs.ErrInUse</code> and leaving the VFS registered. It used to free the VFS the open connection still called through, so the next query crashed the process or read through freed memory. Close the databases first, then the <code>FS</code>.</li> <li>Fix handle reuse in <code>modernc.org/sqlite/vfs</code> on 32-bit targets: after 2^32 file opens in one process the handle counter wrapped and could overwrite a live entry, such as a file system registered at start-up, and crash. 64-bit targets were not affected.</li> <li><strong>The pluggable page cache now panics when a <code>Cache</code> breaks its contract</strong> by returning nil, or a different <code>Page</code>, from <code>Fetch</code> for a page SQLite still holds pinned. It used to free memory SQLite was still using, corrupting the database without an error. Only a <code>Cache</code> implementation with that bug is affected; <code>modernc.org/sqlite/pcache</code> is not.</li> <li>Document three limits of the pluggable page cache on <code>RegisterPageCache</code> and <code>Cache</code>: it cannot be combined with <code>modernc.org/sqlite/vec</code>, <code>PageCache.Create</code> may be called concurrently, and under <code>cache=shared</code> a <code>Cache</code> is called from several goroutines. Documentation only.</li> <li>Document in the package documentation that state set on a pooled connection is inherited by the next caller to borrow it, and that a connection reached through <code>sql.Conn.Raw</code> is not safe for concurrent use. Documentation only.</li> <li>Add <code>StrictPragmas</code>, <strong>opt-in and off by default</strong>: once enabled, a connection whose <code>_pragma</code> DSN value holds more than one SQL statement fails to open with <code>ErrMultiStatementPragma</code>, before any DSN parameter is applied. A <code>_pragma</code> value runs as SQL text, so anything after a <code>;</code> runs too. Recommended for any application whose DSN is not a compile-time constant.</li> <li>Document SQLite's own URI query parameters on <code>Driver.Open</code>: <code>mode</code>, <code>cache</code>, <code>immutable</code>, <code>nolock</code>, <code>psow</code> and <code>modeof</code>, which have always worked in a DSN starting with <code>file:</code>, and the trap that a plain file name has its query stripped before SQLite sees it, so <code>/path/to.db?mode=ro</code> opens read-write. Resolves [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/257";>#257</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/257";>https://gitlab.com/cznic/sqlite/-/issues/257</a>). Documentation only.</li> <li>Add <code>SECURITY.md</code>, the vulnerability reporting policy: three private channels, what is in scope, that only the latest release is supported, and how a confirmed report is disclosed, including an entry in the Go vulnerability database so <code>govulncheck</code> reports it. <code>IRP.md</code>, linked from it, is the maintainers' incident response plan. Documentation only.</li> <li>Add <code>CONTRIBUTING.md</code>: where to send a merge request, which files are generated and must not be edited by hand, how to build and test across the 20 supported targets, and the <code>AUTHORS</code>/<code>CONTRIBUTORS</code> convention. Documentation only.</li> <li>Ship <code>LICENSE-3RD-PARTY.md</code>, a transitively flattened inventory of every third-party component this module carries with all seventeen license texts in full, and a Software Bill of Materials, <code>sbom.cdx.json</code> (CycloneDX 1.6) and <code>sbom.spdx.json</code> (SPDX 2.3), explained in <code>SBOM.md</code>. Both cover what a module-graph tool cannot see: the transpiled SQLite and <code>sqlite-vec</code> C, and the upstreams <code>modernc.org/libc</code> carries, musl among them. Documentation only.</li> </ul> </li> <li> <p>2026-09-15 v1.59.0:</p> <ul> <li>Bump the pinned <code>modernc.org/libc</code> to <a href="https://gitlab.com/cznic/libc/-/tags/v1.75.7";>v1.75.7</a> and re-vendor <code>lib/</code> and <code>vec/</code>. The transpiled SQLite is unchanged, still 3.53.4. On the Linux targets the new libc replaces transpiled musl <code>memcpy</code>, <code>memmove</code>, <code>memset</code>, <code>memcmp</code> and <code>strlen</code> with native Go, cutting CPU time on query-heavy workloads by up to a third; see the new Performance section below. As always, downstream <code>go.mod</code> files must pin the same <code>modernc.org/libc</code> version this repository's <code>go.mod</code> does; see [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/177";>#177</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/177";>https://gitlab.com/cznic/sqlite/-/issues/177</a>).</li> <li>Hand user-defined function and aggregate callbacks a pooled <code>*FunctionContext</code> instead of allocating a fresh one per call, removing the last driver-side allocation per invocation. Like the argument slice, it is valid only for the duration of the callback and must not be retained past its return. Updates [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/226";>#226</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/226";>https://gitlab.com/cznic/sqlite/-/issues/226</a>). See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/137";>#137</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/137";>https://gitlab.com/cznic/sqlite/-/merge_requests/137</a>).</li> <li>Add regression tests pinning the identity and the pooling of that context. See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/138";>#138</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/138";>https://gitlab.com/cznic/sqlite/-/merge_requests/138</a>), thanks Ian Chechin!</li> <li>Add a Performance section to the package documentation: measured CPU-time ratios of this driver against the same SQLite compiled from C, where the gap comes from, and the two consequences for applications — index the columns that <code>ORDER BY</code>, <code>GROUP BY</code> and <code>WHERE</code> use, and bound the <code>database/sql</code> pool with <code>SetMaxOpenConns</code>.</li> </ul> </li> <li> <p>2026-09-01 v1.58.0:</p> <ul> <li>Upgrade to <a href="https://sqlite.org/releaselog/3_53_4.html";>SQLite 3.53.4</a>. It carries upstream's own fix for the journal-rollback data-corruption bug, so the local super-journal patch v1.56.0 introduced is dropped; recovery behavior is unchanged. Also bumps the pinned <code>modernc.org/libc</code> to v1.75.6; as always, downstream modules must pin the same version this one does, see [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/177";>#177</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/177";>https://gitlab.com/cznic/sqlite/-/issues/177</a>).</li> <li>Add opt-in support for <strong>Linux Open File Description (OFD) locks</strong> on database files, <strong>off by default</strong>; without opting in, locking behavior is byte-for-byte that of previous releases. A POSIX record lock is owned by the (process, inode) pair, so any <code>Close</code> of any descriptor of the database file anywhere in the process silently strips SQLite's locks; OFD locks survive that. Enable it process-wide with <code>MODERNC_SQLITE_OFD_LOCK=1</code> in the environment, or with the new <code>OFDLocking(true)</code> before the first connection is opened; <code>OFDLockingEnabled</code> reports the mode in effect, and the new <code>ErrOFDLockingTooLate</code> and <code>ErrOFDLockingUnavailable</code> report a switch attempted too late and a platform or filesystem without the feature. Why it is process-wide rather than a DSN parameter, what WAL's <code>-shm</code> coordination still uses, and the <code>/proc/locks</code> measurements behind the design a re in [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/255";>#255</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/255";>https://gitlab.com/cznic/sqlite/-/issues/255</a>).</li> <li>Resolves [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/255";>#255</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/255";>https://gitlab.com/cznic/sqlite/-/issues/255</a>). See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/136";>#136</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/136";>https://gitlab.com/cznic/sqlite/-/merge_requests/136</a>), thanks Nathan Herring (<a href="https://gitlab.com/technosloth";><code>@technosloth</code></a>), and thanks Gani Georgiev (<a href="https://gitlab.com/ganigeorgiev";><code>@ganigeorgiev</code></a>) for pressing the opt-in default!</li> </ul> </li> <li> <p>2026-08-19 v1.57.0:</p> <ul> <li>Add an opt-in <code>_defensive</code> DSN query parameter turning on SQLite's defensive mode for the connection. On such a connection <code>PRAGMA writable_schema=ON</code>, <code>PRAGMA journal_mode=OFF</code> and <code>PRAGMA schema_version=N</code> become silent no-ops, and writes to a virtual table's shadow tables and to <code>sqlite_dbpage</code> fail. It is a hardening measure, not a sandbox for hostile database files, for which it is only one of the steps <a href="https://www.sqlite.org/security.html";>SQLite recommends</a>, and it is a property of the connection, not of the file. Absent, or <code>_defensive=0</code>, nothing changes.</li> <li>Reject <code>_defensive=1</code> together with <code>_journal_mode=OFF</code> (or <code>_journal=OFF</code>) instead of opening a connection in which neither was honoured: SQLite turns that PRAGMA into a no-op that still reports success. Only DSNs using the new parameter can be affected. See [GitHub pull request <a href="https://gitlab.com/cznic/sqlite/-/work_items/6";>#6</a>](<a href="https://redirect.github.com/modernc-org/sqlite/pull/6";>modernc-org/sqlite#6</a>), thanks wsman!</li> <li>Ship the <a href="https://github.com/asg017/sqlite-vec";>sqlite-vec</a> license notice this module has been missing since <code>vec/</code> arrived in v1.47.0. sqlite-vec is Copyright (c) 2024 Alex Garcia, dual-licensed Apache-2.0 OR MIT and used here under MIT; the text now ships as <code>LICENSE-SQLITE_VEC</code>, and <code>make vendor</code> fails rather than quietly dropping it.</li> <li><strong>The SQLite notice is renamed from <code>SQLITE-LICENSE</code> to <code>LICENSE-SQLITE</code></strong>; update any direct links to it. Its contents are unchanged. The rename is what makes <code>go mod vendor</code> carry both notices into downstream <code>vendor/</code> trees: it selects license files by name prefix, so a name merely ending in <code>LICENSE</code> was never propagated.</li> <li>Let a caller-constructed <code>Driver</code> register its own functions, collations and virtual table modules, through new <code>RegisterFunction</code>, <code>RegisterScalarFunction</code>, <code>RegisterDeterministicScalarFunction</code>, <code>RegisterCollationUtf8</code> and <code>RegisterModule</code> methods plus <code>Must*</code> variants, and let <code>vtab.RegisterModule</code> honour its <code>db</code> argument. <strong>Behavior change</strong>: <code>vtab.RegisterModule(db, ...)</code> where <code>db</code> was opened on a caller-constructed <code>Driver</code> used to discard <code>db</code> and land on the registered <code>sqlite</code> driver, reaching every connection in the process; it now lands on that <code>Driver</code> alone, so a <code>sql.Open("sqlite")</code> connection that used to resolve such a module gets <code>no such module</code>. Everything else is additive, and the isolating change discussed in [GitLab issue <a href="https://gitlab.c om/cznic/sqlite/-/work_items/254">#254</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/254";>https://gitlab.com/cznic/sqlite/-/issues/254</a>) is deliberately not made here. See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/135";>#135</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/135";>https://gitlab.com/cznic/sqlite/-/merge_requests/135</a>), thanks Ian Chechin!</li> <li>Promote <code>freebsd/386</code>, <code>freebsd/arm</code> and <code>netbsd/amd64</code> from experimental to fully supported. The package documentation's platform table had carried seventeen entries while this module shipped, cross-built and tested twenty; all three have been in the builder matrix since v1.53.0 and pass the full suite on this release's commit. Documentation only — <code>lib/</code> is byte-for-byte what v1.56.0 shipped.</li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://gitlab.com/cznic/sqlite/commit/b122d0417c01508beb55158faedeb64a0c5bfd8a";><code>b122d04</code></a> conn: bind statement arguments in linear time</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/7d5a37693ebb757dcae7aa0f90d7ff833d3807e8";><code>7d5a376</code></a> CHANGELOG.md: slim the v1.60.0 section</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/a604165aed43884e6cf353a9f1a054de9a459b34";><code>a604165</code></a> CHANGELOG.md: the SEH emulation, the re-vendor and the removed lib constants;...</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/fb4aac493098a52c9e0d6a018f79f1835161ce0b";><code>fb4aac4</code></a> vendor.json: stamp lib/ from libsqlite3 v1.15.0 and vec/ from libsqlite_vec v...</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/0f7ae7d71679039a81e4f9d93d41fdfec8b81831";><code>0f7ae7d</code></a> Merge branch 'master' into seh-emulation</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/2e4332404f5cc1be407523259068e5752fc9d22e";><code>2e43324</code></a> lib: re-vendor from modernc.org/libsqlite3 v1.15.0 (SEH emulation), pin libc ...</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/50380ee041c17a22737c144f87eba4bb6461af1f";><code>50380ee</code></a> lib, tests: Go side of the wal.c SEH emulation for Windows in-page faults (<a href="https://gitlab.com/cznic/sqlite/-/work_items/221";>#221</a>)</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/4552e53ec5342cbb08542166c75c1f381ccdd84d";><code>4552e53</code></a> Merge branch 'vendor-stamp' into 'master'</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/377517737a53611045ebe5ace90dbacb03f35601";><code>3775177</code></a> Makefile, doc.go, IRP.md: VENDORFLAGS for debug builds; name every refusal</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/86c97d49058dda7e509f2248862f656ace2e083b";><code>86c97d4</code></a> CHANGELOG.md: link merge request !140</li> <li>Additional commits viewable in <a href="https://gitlab.com/cznic/sqlite/compare/v1.59.0...v1.60.1";>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]
