Upgrade sqlite3 to version 1.5.2

[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.2) · Repo · Changelog

Release Notes

1.5.2

1.5.2 / 2022-10-01

Packaging

This version correctly vendors the tarball for sqlite v3.39.4 in the vanilla "ruby" platform gem package, so that users will not require network access at installation.

v1.5.0 and v1.5.1 mistakenly packaged the tarball for sqlite v3.38.5 in the vanilla "ruby" platform gem, resulting in downloading the intended tarball over the network at installation time (or, if the network was not available, failure to install). Note that the precompiled native gems were not affected by this issue. [#352]

---

sha256 checksums:

94626203958f9abf5e7d28b0337af6d00fb10cabfc3d65e70eb95b878080a812  sqlite3-1.5.2-aarch64-linux.gem
ada7a8ec6b13165ebb56dfc8df9f896d2b41c78e92e2ba0b5bca969b6c376e1d  sqlite3-1.5.2-arm-linux.gem
472d837f79273bbfb7d626c787a0f3e9f0bd0a3855ed5bfee1ef70bee8808ced  sqlite3-1.5.2-arm64-darwin.gem
750bf833b72550244c672cb3467b68b5c89b3e8be2c893a2749cdbc3841ee898  sqlite3-1.5.2-x64-mingw-ucrt.gem
e750e17784cd76b59f5dd9a3366f9b0d76626872700f0f59194f2f4c439cbb01  sqlite3-1.5.2-x64-mingw32.gem
caf0a7717375addb46157b1090ad02316a9491531d69e2389f56058ce784518e  sqlite3-1.5.2-x86-linux.gem
caff6c75b13874ce828514a95aa437744e042390fdeb0f73decde16235d3fe2f  sqlite3-1.5.2-x86_64-darwin.gem
245f2ef5dd9c6a2b3df41b4af41fa659c8917d0cc231d4c1b03b4d199ae412e7  sqlite3-1.5.2-x86_64-linux.gem
9b3153b5703b4619534135c16ff7c4e8ba1adbd8548ff61bb4a002dd632bcd5e  sqlite3-1.5.2.gem

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

Commits

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

• version bump to v1.5.2
• Merge pull request #352 from sparklemotion/351-fix-tarball-packaging
• fix: native.rake and test-gem-file-contents use dependencies.yml
• refactor: extract mini_portile recipe config to dependencies.yml

---

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 #73.