Bump sqlite3 from 1.4.4 to 1.5.0

[dependabot]

Bumps sqlite3 from 1.4.4 to 1.5.0.

Release notes

Sourced from sqlite3's releases.

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

---

... (truncated)

Changelog

Sourced from sqlite3's changelog.

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

Commits

• 31ea008 version bump to 1.5.0 (final)
• 23721a7 rb_gc_register_address() must be called after the variable was assigned (#345)
• 6607e64 Merge pull request #342 from sparklemotion/flavorjones-update-sqlite-3.39.3
• 10f4308 dep: update packaged sqlite3 to v3.39.3
• bf63f77 doc: fix sqlite3 docs link in CHANGELOG
• 2544e58 version bump to v1.5.0.rc2 (release candidate)
• 1cfa1c1 Merge pull request #341 from sparklemotion/flavorjones-compiler-optimization
• d77cf57 perf: use -O2 compiler optimizations
• e27f9b0 Merge pull request #340 from sparklemotion/339-load-extension-segfault
• 31785dd fix: Database#load_extension check argument type
• Additional commits viewable in compare view

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 commands and options

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)