Log message:
databases/ruby-sqlite3: update to 2.4.1

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

* Prevent unnecessary "Invalid Reference" warnings from the ForkSafety
  module when GC runs during the "after fork" hook.  #592 @flavorjones

Log message:
databases/ruby-sqlite3: update to 2.4.0

2.3.0 (2024-11-20)

Added

* The SQLITE_DBPAGE extension is now enabled by default, which implements an
  eponymous-only virtual table that provides direct access to the underlying
  database file by interacting with the pager.  See
  https://www.sqlite.org/dbpage.html for more information.  [#578]
  @flavorjones

* The DBSTAT extension is now enabled by default, which implements a
  read-only eponymous virtual table that returns information about the
  amount of disk space used to store the content of an SQLite database.  See
  https://sqlite.org/dbstat.html for more information.  [#580] @pawurb
  @flavorjones

* Database#optimize which wraps the pragma optimize; statement. Also added
  Constants::Optimize to allow advanced users to pass a bitmask of options.
  See https://www.sqlite.org/pragma.html#pragma_optimize. [#572] @alexcwatt
  @flavorjones

* SQLite3::VERSION_INFO contains a bag of metadata about the gem and the
  sqlite library used.  SQLite3::SQLITE_PACKAGED_LIBRARIES and
  SQLite3::SQLITE_PRECOMPILED_LIBRARIES indicate how the gem was built.
  [#581] @flavorjones

Fixed

* Database#encoding= support for switching the database encoding to
  UTF-16BE, which has been broken since Database#encoding= was introduced in
  v1.3.12 in 2016.  [#575] @miyucy

* Omit mention of the pkg-config gem when failing to build from source,
  since it is not used.  [#358] @flavorjones

2.3.1 (2024-11-25)

Dependencies

* Vendored sqlite is updated to v3.47.1 [#589] @flavorjones

2.4.0 (2024-12-03)

Added

* Database#load_extension now accepts any object that responds to #to_path,
  in addition to String filesystem paths.  [#586] @flavorjones

* Database.new now accepts an extensions: parameter, which is an array of
  SQLite extensions that will be loaded during initialization.  The array
  may contain String filesystem paths and objects that respond to #to_path.
  [#586] @flavorjones

Log message:
*: recursive bump for icu 76 shlib major version bump

Log message:
databases/ruby-sqlite3: update to 2.2.0

2.2.0 (2024-10-30)

Added

* URI filenames are now allowed.  This allows the injection of some behavior
  via recognized query parameters.  See https://www.sqlite.org/uri.html for
  more information.  [#571] @flavorjones

Improved

* SQL Syntax errors during Database#prepare will raise a verbose exception
  with a multiline message indicating with a "^" exactly where in the
  statement the error occurred.  [#554] @fractaledmind @flavorjones

Log message:
*: revbump for icu downgrade

Log message:
*: recursive bump for icu 76.1 shlib bump

Log message:
databases/ruby-sqlite3: update to 2.1.1

2.1.1 (2024-10-22)

Dependencies

* Vendored sqlite is updated to v3.47.0 [#570] @flavorjones

Log message:
databases/ruby-sqlite3: update to 2.1.0

2.1.0 (2024-09-24)

Ruby

* This release drops support for Ruby 3.0. [#563] @flavorjones

Fork safety improvements

Sqlite itself is not fork-safe.  Specifically, writing in a child process to
a database connection that was created in the parent process may corrupt the
database file.  To mitigate this risk, sqlite3-ruby has implemented the
following changes:

* All open writable database connections carried across a fork() will
  immediately be closed in the child process to mitigate the risk of
  corrupting the database file.

* These connections will be incompletely closed ("discarded") which will
  result in a one-time memory leak in the child process.

If it's at all possible, we strongly recommend that you close writable
database connections in the parent before forking.  If absolutely necessary
(and you know what you're doing), you may suppress the fork safety warnings
by calling SQLite3::ForkSafety.suppress_warnings!.

See the README's "Fork Safety" section and adr/2024-09-fork-safety.md for
more information. [#558, #565, #566] @flavorjones

Improved

* Use sqlite3_close_v2 to close databases in a deferred manner if there are
  unclosed prepared statements.  Previously closing a database while
  statements were open resulted in a BusyException.  See
  https://www.sqlite.org/c3ref/close.html for more context.  [#557]
  @flavorjones

* When setting a Database busy_handler, fire the write barrier to prevent
  potential crashes during the GC mark phase.  [#556] @jhawthorn

Documentation

* The FAQ.md has been updated to fix some inaccuracies.  [#562] @rickhull