dependabot[bot] opened a new pull request, #1333: URL: https://github.com/apache/arrow-go/pull/1333
Bumps [modernc.org/sqlite](https://gitlab.com/cznic/sqlite) from 1.58.0 to 1.59.0. <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-15 v1.59.1:</p> <ul> <li>Document two properties of connections in the package documentation: state set on a pooled connection -- PRAGMAs set with <code>Exec</code>, ATTACHed databases, temporary tables, anything registered through <code>sql.Conn.Raw</code> -- is inherited by the next caller to borrow it, and a driver connection reached through <code>Raw</code> is not safe for concurrent use even though every connection is opened <code>SQLITE_OPEN_FULLMUTEX</code>. 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 <code>_pragma=foreign_keys(1);ATTACH 'x.db' AS x</code> also attaches, and creates, <code>x.db</code>; the <code>Driver.Open</code> documentation said "a PRAGMA statement" and now says what actually happens. Enabling it is 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>. Every connection is opened with <code>SQLITE_OPEN_URI</code>, so in a DSN starting with <code>file:</code> these have always worked; only the driver's own keys were listed. The docstring also spells out 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. Documentation only.</li> <li>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>).</li> <li>Add <code>IRP.md</code>, an incident response plan: who runs a response when there are two maintainers in different time zones, how a report is scoped across the three layers this module is built from, the fix path for each, and what to do when a released version is itself the problem -- a published Go module version cannot be recalled, so <code>retract</code> plus a new release is the remedy. Linked from <code>SECURITY.md</code>. 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. Contribution guidance previously existed only in <code>GOVERNANCE.md</code> and <code>HACKING.md</code>, neither of which a first-time contributor is likely to open. Documentation only.</li> <li>Add <code>SECURITY.md</code>: report a vulnerability through GitHub private vulnerability reporting, a confidential GitLab issue, or the project's Service Desk address, never a public issue. It states what is in scope -- including transpilation faults, where the generated Go does not faithfully implement the C it came from -- that only the latest release is supported, and that a confirmed report is disclosed through a GitHub advisory, an entry in the Go vulnerability database so <code>govulncheck</code> reports it, and a release note. Documentation only.</li> <li>Ship a Software Bill of Materials: <code>sbom.cdx.json</code> (CycloneDX 1.6) and <code>sbom.spdx.json</code> (SPDX 2.3), both validated against the published schemas, with <code>SBOM.md</code> explaining what they cover. They name what an SBOM built from the module graph cannot see -- the transpiled SQLite 3.53.4 and <code>sqlite-vec</code> C, and the upstreams <code>modernc.org/libc</code> vendors, musl among them -- and mark every component as linked into your binary, test-only, or compiled into nothing. Documentation only.</li> <li>Ship <code>LICENSE-3RD-PARTY.md</code>, a transitively flattened inventory of every third-party component this module carries: the whole Go module graph, the transpiled SQLite and <code>sqlite-vec</code> C that no <code>go.mod</code> names, and the upstreams <code>modernc.org/libc</code> carries in turn, musl among them. It reproduces all seventeen distinct license texts in full and separates what is linked into your binary from what only appears in the module graph. The <code>LICENSE</code> name prefix is what makes <code>go mod vendor</code> carry it into downstream <code>vendor/</code> trees. 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> <li> <p>2026-08-03 v1.56.0:</p> <ul> <li>Re-vendor the transpiled sources, picking up <code>modernc.org/libsqlite3</code>'s patch for an <strong>upstream data-corruption bug in SQLite 3.53.3's journal rollback</strong>. A crash during the commit of a multi-database (ATTACH) transaction can leave a hot journal whose zeroed super-journal name still validates, so <code>pager_playback()</code> deletes it without playing it back and leaves the database corrupted. Not a transpilation artifact: a plain gcc build of stock 3.53.3 fails on the same bytes. The SQLite version is unchanged at <a href="https://sqlite.org/releaselog/3_53_3.html";>3.53.3</a>, every supported target carries the patch, and it will be dropped once upstream ships its own fix.</li> <li>Two targets change beyond that patch. <code>linux/s390x</code> now allocates C bit-fields MSB-first as the big-endian ABI requires, from <code>modernc.org/cc/v4</code> v4.29.1. <code>linux/riscv64</code> was regenerated on a host running GCC 11.4.0 rather than 13.3.0, which drops some unreferenced compiler-predefined macro constants and changes what <code>PRAGMA compile_options</code> reports; no SQLite code generation differs. Every other target is byte-identical to v1.55.0 apart from the patch above.</li> <li>Bump the pinned <code>modernc.org/libc</code> to v1.74.4 and the remaining dependencies to their current releases. v1.74.2 and v1.74.3 are retracted upstream over a <code>freeaddrinfo</code> lock leak that deadlocks name resolution, and v1.74.4 is the fix. As always, downstream modules must pin the same <code>modernc.org/libc</code> 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 <code>NewConnector</code>, returning a <code>database/sql/driver.Connector</code> for use with <code>sql.OpenDB</code>. It opens the same connections <code>sql.Open("sqlite", dsn)</code> does, from the same registered driver, so every function, collation, connection hook and virtual table module registered through this package applies to them. It exists for callers that need to interpose on the physical connections <code>database/sql</code> opens — tracing, metrics, connection-scoped setup — for which the alternative was <code>sql.Register</code>, which is process-global, panics on a repeated name and cannot be undone. A runnable sample is in <code>examples/connector</code>. Resolves [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/253";>#253</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/253";>https://gitlab.com/cznic/sqlite/-/issues/253</a>), thanks Alessandro Segala (<a href="https://gitlab.com/ItalyPaleAle";><code>@ItalyPaleAle< /code></a>)!</li> <li>Documentation sweep. <code>openbsd/amd64</code> and <code>openbsd/arm64</code> join the supported platforms table, the <code>vfs</code> DSN query parameter is documented alongside the others on <code>Driver.Open</code>, the stale <code>go generate</code> and <code>GO_GENERATE</code> instructions are replaced by <code>modernc.org/libsqlite3</code> and <code>make vendor</code>, and <code>vec</code> and <code>vfs</code> gained the package doc comments they were missing. A caller-constructed <code>sqlite.Driver</code> is now documented as <em>not</em> being the driver this package registers as <code>"sqlite"</code>: it carries none of the package-level functions and collations, so it can evaluate <code>upper(x)</code> or <code>date(x)</code> differently. Documentation only.</li> </ul> </li> <li> <p>2026-07-20 v1.55.0:</p> <ul> <li>Add <code>github.com/mattn/go-sqlite3</code>-compatible shorthand DSN query parameters to ease migration from that driver: <code>_busy_timeout</code>/<code>_timeout</code>, <code>_foreign_keys</code>/<code>_fk</code>, <code>_journal_mode</code>/<code>_journal</code>, <code>_synchronous</code>/<code>_sync</code>, <code>_auto_vacuum</code>/<code>_vacuum</code> and <code>_query_only</code>, each setting the correspondingly named PRAGMA. Values are validated against the same set <code>mattn/go-sqlite3</code> accepts and an unrecognized one fails the connection, so a typo cannot silently downgrade durability. <strong>Review DSNs carried over from that driver before upgrading</strong>: a key prior releases ignored entirely now takes effect, so <code>_foreign_keys=on</code> begins enforcing constraints and <code>_journal_mode=wal</code> persistently converts the file; and a duration-style <code>_busy_timeout=5s</code> now fails an open that previously succeeded. See [GitLab merge req uest <a href="https://gitlab.com/cznic/sqlite/-/work_items/134";>#134</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/134";>https://gitlab.com/cznic/sqlite/-/merge_requests/134</a>), thanks Toni Spets (<a href="https://gitlab.com/beeper-hifi";><code>@beeper-hifi</code></a>) and Ian Chechin!</li> <li>Validate every DSN query parameter before applying any of them. Parameters were checked as each was reached, so a DSN rejected for a later parameter had already executed the PRAGMAs ahead of it: <code>file:x.db?_journal_mode=wal&_synchronous=bogus</code> failed the connection and yet left <code>x.db</code> converted to WAL. A failed <code>Open</code> now leaves the database as it found it. The accepted values are unchanged. <code>_pragma</code> remains the sole exception, since its values are executed verbatim and can only be rejected by SQLite as they run.</li> </ul> </li> <li> <p>2026-07-15 v1.54.0:</p> <ul> <li>Upgrade to <a href="https://sqlite.org/releaselog/3_53_3.html";>SQLite 3.53.3</a>. This also bumps the pinned <code>modernc.org/libc</code> to v1.74.1; as always, downstream modules must pin the exact same <code>modernc.org/libc</code> version this module's <code>go.mod</code> pins (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>Under the opt-in <code>_texttotime</code> DSN parameter, best-effort parse date-shaped TEXT values from columns SQLite reports with an empty declared type — aggregates and expressions over a date column (<code>MAX(d)</code>, <code>COALESCE(d, ...)</code>, <code>upper(d)</code>, <code>d || ''</code>), subqueries, and typeless real columns (<code>CREATE TABLE t(x)</code>) — into <code>time.Time</code>, instead of delivering them as a raw string that <code>Scan</code> cannot store into a <code>*time.Time</code>. The existing declared <code>DATE</code>/<code>DATETIME</code>/<code>TIME</code>/<code>TIMESTAMP</code> path is unchanged; this only adds the empty-decltype case. The conversion is strictly best-effort: a value that does not parse as a time falls through to the original string, so no <code>Scan</code> that worked before can newly fail. <code>ColumnTypeScanType</code> continues to report <code>string</code> for empty-decltype columns, since the declared type cannot prov e the column is temporal. Without <code>_texttotime</code> the behavior is byte-for-byte unchanged. Resolves [GitLab issue <a href="https://gitlab.com/cznic/sqlite/-/work_items/248";>#248</a>](<a href="https://gitlab.com/cznic/sqlite/-/issues/248";>https://gitlab.com/cznic/sqlite/-/issues/248</a>).</li> <li>See [GitLab merge request <a href="https://gitlab.com/cznic/sqlite/-/work_items/133";>#133</a>](<a href="https://gitlab.com/cznic/sqlite/-/merge_requests/133";>https://gitlab.com/cznic/sqlite/-/merge_requests/133</a>), thanks Ian Chechin!</li> </ul> </li> <li> <p>2026-06-21 v1.53.0:</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://gitlab.com/cznic/sqlite/commit/c96a4e6cb22254bf70026502a781a54a053c2cf0";><code>c96a4e6</code></a> CHANGELOG.md: document the libc v1.75.7 bump and the Performance section</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/35c446e7366d96996563e6c11e4331a9a24a6833";><code>35c446e</code></a> update dependencies, make vendor</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/9ad02acfd2d7b296bf3a4fd769ccac9e369c9511";><code>9ad02ac</code></a> Merge branch 'udf-context-tests' into 'master'</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/d6d84a97943928b2ee7e02c94b9314032260d2d6";><code>d6d84a9</code></a> sqlite: pin the identity and the pooling of the FunctionContext in tests</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/59ec397ba01a0e261203a4787e705f40e8176bd5";><code>59ec397</code></a> doc.go: add a Performance section with measured driver-vs-C ratios</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/51cbcbff3abb241103b2d4507ffaa5234f3b3111";><code>51cbcbf</code></a> Merge branch 'udf-call-pool' into 'master'</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/e390a0ca584a320680a5ad02cd5a5eab2d9ae68f";><code>e390a0c</code></a> sqlite: pool the FunctionContext handed to UDF and aggregate callbacks</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/38af58174508625ec5c678ae118421303f6992d1";><code>38af581</code></a> doc.go, README.md: point readers at CHANGELOG.md</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/37e55e472f4f1f5c17726c4385b02c0e98ba4895";><code>37e55e4</code></a> CHANGELOG.md: reconstruct the missing entries for v1.38.1 through v1.44.1 and...</li> <li><a href="https://gitlab.com/cznic/sqlite/commit/2f7234fc73d8954e8a726890b1c43ff847daa32a";><code>2f7234f</code></a> AUTHORS, CONTRIBUTORS: add Nathan Herring; CHANGELOG.md: credit him by name</li> <li>See full diff in <a href="https://gitlab.com/cznic/sqlite/compare/v1.58.0...v1.59.0";>compare view</a></li> </ul> </details> <br /> <details> <summary>Most Recent Ignore Conditions Applied to This Pull Request</summary> | Dependency Name | Ignore Conditions | | --- | --- | | modernc.org/sqlite | [>= 1.34.a, < 1.35] | </details> [](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]
