notebook

notebook copied to clipboard

Sourced from sqlite3's releases.

2.7.0 / 2025-06-09

• Vendored sqlite is updated to v3.50.1 (from v3.49.1). #630 @​flavorjones

8e4ca6fee1e635092fc56c951274b732e5d3186526b3db43286ed3cacf9d2c70  sqlite3-2.7.0-aarch64-linux-gnu.gem
ffa253517b62bc241b91016402e5b44087390bf7e89ba4820eb7f3c28cf76ce6  sqlite3-2.7.0-aarch64-linux-musl.gem
b79d76bd496688f45bd43069f3475285f3303d00a2a9c61cd4fc915350aa20ac  sqlite3-2.7.0-arm64-darwin.gem
720abe303b75c55f98ce5d0e9ab32cb45570d3ec99490953fa807c45d0fd3f6c  sqlite3-2.7.0-arm-linux-gnu.gem
c2b437c54df1debf41e523b02df4f0324e2891f34e12deb4d97db168d6c717ed  sqlite3-2.7.0-arm-linux-musl.gem
dab87a41172e2397909847a9d6251c6251ac1e9942a026569af17e77d645ebf0  sqlite3-2.7.0.gem
b7d18b29bcc92ca67439c4fe85635449e1eae0313ccfa5a6299de362c146a1a5  sqlite3-2.7.0-x64-mingw-ucrt.gem
5a625bb886d2b594b9c90f11852128777b8949aa8a78c3da95a7e122e206a056  sqlite3-2.7.0-x86_64-darwin.gem
6d7a41bbfc2319bc7e43e944a97a8b15de91c71098bc1d8f4c91c8b719b1c940  sqlite3-2.7.0-x86_64-linux-gnu.gem
b6ff52adad59521918854adf5784dc57bc8853fdcd904b66fd53af7b683b4042  sqlite3-2.7.0-x86_64-linux-musl.gem
74524de4ada6c97d6526055fd04c194c42d8b89f426a8b24737b61ba2dfb9e95  sqlite3-2.7.0-x86-linux-gnu.gem
53f098cc7a0abcb9852faae7ca79920244dffbb7257f3c1508c277516af1d558  sqlite3-2.7.0-x86-linux-musl.gem

v2.6.0

2.6.0 / 2025-02-20

Dependencies

• Vendored sqlite is updated to v3.49.1 (from v3.47.2). #605 @​flavorjones
• Updated to rake-compiler-dock v1.9.1. #610 @​flavorjones

Important note for Window users

Loading extensions is not available on Windows when using the precompiled native gems or compiling the vendored sqlite library from source, starting with sqlite3-ruby v2.6.0.

Sqlite 3.48.0 and later have dramatically changed the "autoconf amalgamation" that is vendored in this gem. Specifically, the configuration is no longer actually autoconf, but some scripts that emulate autoconf's interface and behavior.

Although this mostly "just worked", we're having a problem resolving the libraries necessary for loading extensions. As a result, starting with sqlite3-ruby v2.6.0, extensions cannot be loaded on Windows when using precompiled native gems or when compiling the vendored sqlite library.

If you are willing and able to help fix this, let us know at sparklemotion/sqlite3-ruby#618.

febc29bd7037695779d6b482fac7f7add9af7b420a1c5120ccff79213415975e  sqlite3-2.6.0-aarch64-linux-gnu.gem
d235cf89ba96067462562bc71adf5309363a9fee09a1864667f45799f26825ca  sqlite3-2.6.0-aarch64-linux-musl.gem
88a793bf0010339e85657e460ab3ad2c7e9ee5d0e468b9dea383ff1039380056  sqlite3-2.6.0-arm64-darwin.gem
5f7e1160ad6bf6bfc0d42d1a7de95554b00a5dc7375953070d9633fedadc93bd  sqlite3-2.6.0-arm-linux-gnu.gem
</tr></table> 

... (truncated)

Sourced from sqlite3's changelog.

2.7.0 / 2025-06-09

• Vendored sqlite is updated to v3.50.1 (from v3.49.1). #630 @​flavorjones

2.6.0 / 2025-02-20

Dependencies

• Vendored sqlite is updated to v3.49.1 (from v3.47.2). #605 @​flavorjones
• Updated to rake-compiler-dock v1.9.1. #610 @​flavorjones

Important note for Window users

Loading extensions is not available on Windows when using the precompiled native gems or compiling the vendored sqlite library from source, starting with sqlite3-ruby v2.6.0.

Sqlite 3.48.0 and later have dramatically changed the "autoconf amalgamation" that is vendored in this gem. Specifically, the configuration is no longer actually autoconf, but some scripts that emulate autoconf's interface and behavior.

Although this mostly "just worked", we're having a problem resolving the libraries necessary for loading extensions. As a result, starting with sqlite3-ruby v2.6.0, extensions cannot be loaded on Windows when using precompiled native gems or when compiling the vendored sqlite library.

If you are willing and able to help fix this, let us know at sparklemotion/sqlite3-ruby#618.

2.5.0 / 2024-12-25

Ruby

This release introduces native gem packages that include Ruby 3.4.

2.4.1 / 2024-12-08

Dependencies

• Vendored sqlite is updated to v3.47.2 #593 @​flavorjones

  The description from the upstream maintainers is:

  SQLite version 3.47.2, now available, fixes an important bug that first appeared in the 3.47.0 release. In SQLite versions 3.47.0 and 3.47.1, if you try to convert a string into a floating-point value and the first 16 significant digits of the value are exactly "1844674407370955", then the floating-point number generated might be incorrect. The problem only affects x64 and i386 CPUs, so it does not affect you if you are running on ARM. And it only affects releases 3.47.0 and 3.47.1. If you are running SQLite versions 3.47.0 or 3.47.1, then upgrading is recommended.

  Saving you a click, you should upgrade if you're running sqlite3-ruby v2.1.1 or later.

Fixed

... (truncated)

• 782653e version bump to v2.7.0
• 5a97532 Merge pull request #630 from sparklemotion/flavorjones/dep-sqlite-3.50.1
• d110815 dep: update vendored sqlite to 3.50.1
• bbef088 Merge pull request #629 from sparklemotion/dependabot/bundler/rdoc-6.14.0
• fbb9001 build(deps-dev): update rdoc requirement from 6.13.1 to 6.14.0
• 402aa1f doc: document Rails 8.1 supports the name of an extension
• a0dd5c8 Merge pull request #626 from sparklemotion/dependabot/bundler/rake-compiler-1...
• a3eb396 build(deps-dev): update rake-compiler requirement from 1.2.9 to 1.3.0
• 1acf341 Merge pull request #625 from sparklemotion/dependabot/bundler/rdoc-6.13.1
• a4c958d build(deps-dev): update rdoc requirement from 6.13.0 to 6.13.1
• Additional commits viewable in compare view

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 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)