Upgrade sqlite3 to version 1.5.0

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sqlite3 (~> 1.3.11 → ~> 1.5.0) · Repo · Changelog

Release Notes

1.5.0

1.5.0 / 2022-09-08

Packaging

Faster, more reliable installation

Native (precompiled) gems are available for Ruby 2.6, 2.7, 3.0, and 3.1 on all these platforms:

• aarch64-linux
• arm-linux
• arm64-darwin
• x64-mingw32 and x64-mingw-ucrt
• x86-linux
• x86_64-darwin
• x86_64-linux

If you are using one of these Ruby versions on one of these platforms, the native gem is the recommended way to install sqlite3-ruby.

See the README for more information.

More consistent developer experience

Both the native (precompiled) gems and the vanilla "ruby platform" (source) gem include sqlite v3.39.3 by default.

Defaulting to a consistent version of sqlite across all systems means that your development environment behaves exactly like your production environment, and you have access to the latest and greatest features of sqlite.

You can opt-out of the packaged version of sqlite (and use your system-installed library as in versions < 1.5.0). See the README for more information.

Release notes for this version of sqlite

Rubies and Platforms

• TruffleRuby is supported.
• Apple Silicon is supported (M1, arm64-darwin).
• vcpkg system libraries supported. [#332] (Thanks, @MSP-Greg!)

Added

• SQLite3::SQLITE_LOADED_VERSION contains the version string of the sqlite3 library that is dynamically loaded (compare to SQLite3::SQLITE_VERSION which is the version at compile-time).

Fixed

• SQLite3::Database#load_extensions now raises a TypeError unless a String is passed as the file path. Previously it was possible to pass a non-string and cause a segfault. [#339]

---

sha256 checksums:

075f634aefaf00bcec3186ac01527315df8de4c7b67636aee286d3878413ca1b  sqlite3-1.5.0-aarch64-linux.gem
07803d427d839badacd9eae0b3f91496b730dc91731b86b8a29a140d40e7c7db  sqlite3-1.5.0-arm-linux.gem
a0c849dcbf7496e521a6de8ff0f47a30ce9d3403ce85f483705a7fd8a88b52ef  sqlite3-1.5.0-arm64-darwin.gem
58cc3f1a933a7392e07d8f3f8deb09b0fe884a6ee7b292b62d13ead1bd2eb1c5  sqlite3-1.5.0-x64-mingw-ucrt.gem
975abf40f39f4277ce695a9ecdaa155f47c704ffe9f96c30a5fed13b7dbe655f  sqlite3-1.5.0-x64-mingw32.gem
11a9a51e2cd2dafecbaef2d95e2e22a0fc77bcf3b00826367ae41d69573d60ab  sqlite3-1.5.0-x86-linux.gem
e89b9f958f5ac658de66f5e654dab898b8bcc53c5a0f11b58eed9ce6baea433f  sqlite3-1.5.0-x86_64-darwin.gem
cd996d8fe08244b9bcc81f217eb67171cb6df26d6c5cff2bfdade09248e1842b  sqlite3-1.5.0-x86_64-linux.gem
8eeb6dab3c7ff6b1aa88f8a4a3879b33048c74b309077dba67fa71b72352048a  sqlite3-1.5.0.gem

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 65 commits:

• version bump to 1.5.0 (final)
• rb_gc_register_address() must be called after the variable was assigned (#345)
• Merge pull request #342 from sparklemotion/flavorjones-update-sqlite-3.39.3
• dep: update packaged sqlite3 to v3.39.3
• doc: fix sqlite3 docs link in CHANGELOG
• version bump to v1.5.0.rc2 (release candidate)
• Merge pull request #341 from sparklemotion/flavorjones-compiler-optimization
• perf: use -O2 compiler optimizations
• Merge pull request #340 from sparklemotion/339-load-extension-segfault
• fix: Database#load_extension check argument type
• Merge pull request #337 from sparklemotion/flavorjones-fix-ci-macos-gem-install
• ci: gem-install.yml uses --with-opt-dir for macos system libraries
• ci: trigger github actions on `master`, not `main`
• doc: update CHANGELOG.md
• Merge pull request #334 from eregon/fix-utf16_string_value_ptr-truffleruby
• Fix utf16_string_value_ptr() for TruffleRuby
• Merge pull request #336 from MSP-Greg/00-pr-333-test-versions
• sqlite3-ruby.yml - remove some quotes, reformat include
• sqlite3-ruby.yml macOS - use --with-opt-dir when --enable-system-libraries
• test: assert compiled and loaded versions of sqlite3 are the same
• Merge pull request #332 from MSP-Greg/00-sqlcipher-mswin
• sqlite3-ruby.yml - mswin/sqlcipher - install sqlite3
• ci: trigger github actions on `master`, not `main`
• Merge pull request #330 from sparklemotion/flavorjones-extconf-help-message
• Merge pull request #331 from sparklemotion/flavorjones-update-sqlite3-v3.39.2
• dep: update packaged sqlite3 to v3.39.2
• ext: add --help option and message to extconf.rb
• ext: sqlcipher dir_config params imply system libs and sqlcipher
• Merge pull request #329 from sparklemotion/flavorjones-fix-version-test
• test: skip version string assertion when testing native gems
• version bump to v1.5.0.rc1 (release candidate)
• doc: update CHANGELOG and README
• test: assert on the two version strings
• Merge pull request #328 from sparklemotion/flavorjones-upgrade-sqlite-to-3.39.0
• test: assertions on db path use #realdirpath
• dep: update to sqlite 3.39.0
• test: more exact test for patch file presence
• doc: update CHANGELOG
• Merge pull request #320 from sparklemotion/flavorjones-resurrect-native-gems
• doc: update README and create LICENSE-DEPENDENCIES
• dev: scripts to package gems and assert on their contents
• dev: update .gitignore
• ext: support only ruby >= 2.6
• ext: test native gems on all rcd-supported platforms
• ci: gracefully handle missing version.rb in the gemspec
• ci: cache sqlite3 builds
• refactor: extconf.rb
• dev: annotate the sqlite3 version requirement for sqlite3_open_v2
• ext: ensure sqlcipher is supported as a system library
• doc: convert rdoc files to markdown
• ci: add coverage for mswin windows platform
• ext: support system libraries via `--enable-system-libraries`
• ext: patch automake files to support arm64-darwin systems
• test: use assert_in_delta for floats returned from db funcs
• ci: configure appveyor
• ext: work around MakeMakefile.pkg_config issue in Ruby 3.1
• ext(warnings): quash more compiler warnings
• ext(warnings): use #ifdef to check _MSC_VER instead of #if
• feat: define SQLite3::SQLITE_LOADED_VERSION
• ext: rebuild extconf and native.rake
• ci: simplify basic test pipeline
• gem: manifest management
• dep: remove hoe, prefer a literal gemspec
• Fix required ruby version in gem
• dep: update development dependencies

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #70.