Repository navigation
chore(deps): upgrade modernc.org/sqlite to v1.61.0 - #384
Merged
Merged
Conversation
Take the SQLite driver update from #373 (with modernc.org/libc v1.79.0) and regenerate THIRD_PARTY_NOTICES. Echo is already on v5.4.2 from #375. The duckdb-go v2.20000.0 update in #373 is left out: it moves the native bindings to go.duckdb.org/libduckdb and references duckdb_register_static_extensions, which the pinned DuckDB v2.0.0 static archive does not export, so every DuckDB build fails to link.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Takes the SQLite driver update from #373:
modernc.org/sqlitev1.60.1 → v1.61.0 (withmodernc.org/libcv1.79.0), and regeneratesTHIRD_PARTY_NOTICES. Echo is already on v5.4.2 from #375.The
duckdb-gov2.20000.0 update in #373 is left out. It moves the native bindings togo.duckdb.org/libduckdband referencesduckdb_register_static_extensions, which the pinned DuckDB v2.0.0 static archive does not export, so every DuckDB build fails to link (as #373's CI shows). Adopting it needs a change toscripts/with-duckdb.shand engine verification of its own.Verification
just check: all checks passed (pre-push hook)Supersedes #373.