sqlite3 2.1.0.rc3 → 2.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f625987268dc96e27d1a765bc4a1be109444b46ed293ae332e104c8a988a5682
-  data.tar.gz: 4e85e9d72c9a58569d4f9c54b2a2186c958ced8a354d09274c22d760ad2d895c
+  metadata.gz: 4422ed8d735f1e7c93e10f12391cc5288e86ce6c88082801d2a8802cba59c4b4
+  data.tar.gz: 6cb6d2bdd88e0ad873dc0a897f6f09e46a6d001f72602adf92b7f7b8a6400128
 SHA512:
-  metadata.gz: 6fe89b6a8af14427cf475bbcd68d6a55086d9857c44e7e84d380f0a28cf1e0f0dcfb2512391c48f8eef3ea1a22ab6b9ff9e9557f352ef5648a29d8f2b4adc84e
-  data.tar.gz: f0857a167acb9a134d5d6119b8621d47fdcb91a0eef076624cc4b563088283d0ad0f66cf7bf336e9b117e33422cc87d3b7ee50499e7d580912e0921517d88d27
+  metadata.gz: 2f0baddcbe70a9a8eb22093f707b19226873cbb5e76b3eb9af8b97fd3a8ebda4f1344303ce6220fe297ca4f0edfb5f55eb2585c2832742a315e9c877e69ecaaf
+  data.tar.gz: e843b06be319ae179d1aa99f5d703788d9d65f2e6f36708cc59eb26b8571830113ef531897e53bb9e55d6d074b2814a5ec273bb216384f25dfc453f3bae2cad8

data/CHANGELOG.md

@@ -1,20 +1,6 @@
 # sqlite3-ruby Changelog
 
-## prerelease 2.1.0.rc3 / 2024-09-18
-
-### Improved
-
-- Allow suppression of fork safety warnings. [#566] @flavorjones
-
-
-## prerelease 2.1.0.rc2 / 2024-09-18
-
-### Improved
-
-- Address a performance regression in 2.1.0.rc1.
-
-
-## prerelease 2.1.0.rc1 / 2024-09-18
+## 2.1.0 / 2024-09-24
 
 ### Ruby
 
@@ -28,9 +14,9 @@ Sqlite itself is [not fork-safe](https://www.sqlite.org/howtocorrupt.html#_carry
 - 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 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 "Fork Safety" section and `adr/2024-09-fork-safety.md` for more information. [#558] @flavorjones
+See the README's "Fork Safety" section and `adr/2024-09-fork-safety.md` for more information. [#558, #565, #566] @flavorjones
 
 
 ### Improved
@@ -39,6 +25,11 @@ See the README "Fork Safety" section and `adr/2024-09-fork-safety.md` for more i
 - 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
+
+
 ## 2.0.4 / 2024-08-13
 
 ### Dependencies

data/README.md

@@ -160,7 +160,7 @@ To help protect users of this gem from accidental corruption due to this lack of
 connections in the child will incur a small one-time memory leak per connection, but that's
 preferable to potentially corrupting your database.
 
-Whenever possible, close writable connections in the parent before forking.
+Whenever possible, close writable 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 [./adr/2024-09-fork-safety.md](./adr/2024-09-fork-safety.md) for more information and context.
 

data/lib/sqlite3/version.rb

@@ -1,3 +1,3 @@
 module SQLite3
-  VERSION = "2.1.0.rc3"
+  VERSION = "2.1.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sqlite3
 version: !ruby/object:Gem::Version
-  version: 2.1.0.rc3
+  version: 2.1.0
 platform: ruby
 authors:
 - Jamis Buck