[bundler] Bump the monthly group across 1 directory with 3 updates

[dependabot]

Bumps the monthly group with 3 updates in the / directory: minitest, mocha and sqlite3.

Updates minitest from 5.25.2 to 5.25.4

Changelog

Sourced from minitest's changelog.

=== 5.25.4 / 2024-12-03

• 1 bug fix:

  • Fix for must_verify definition if only requiring minitest/mock (but why?).

=== 5.25.3 / 2024-12-03

• 5 bug fixes:

  • Fixed assert_mock to fail instead of raise on unmet mock expectations.
  • Fixed assert_mock to take an optional message argument.
  • Fixed formatting of unmet mock expectation messages.
  • Fixed missing must_verify expectation to match assert_mock.
  • minitest/pride: Fixed to use true colors with *-direct terminals (bk2204)

Commits

• d84437f prepped for release
• 51cfac5 - Fix for must_verify definition if only requiring minitest/mock (but why?).
• 704d310 prepped for release
• 2d542ff - Fixed formatting of unmet mock expectation messages.
• 212de90 - minitest/pride: Fixed to use true colors with *-direct terminals (bk2204)
• See full diff in compare view

Updates mocha from 2.6.1 to 2.7.1

Changelog

Sourced from mocha's changelog.

2.7.1

External changes

• Deprecate Configuration#stubbing_method_on_nil= (#694)
• Indicate when parameter matcher logic is defined by block passed to Expectation#with (#698, b30e4434)
• Improve documentation for Expectation#with, especially when it is passed a block (#698, #682, #606 & #681)

2.7.0

External changes

• Fail fast if invocation matches never expectation (#679, #678, #490, #131 & #44) - thanks to @​ducmtran & @​davidstosik for reporting

Internal changes

• Workaround for JRuby jar-dependencies issue (#690)
• Ruby v3.4 stacktrace uses single-quote vs backtick (#688 & #689) - thanks to Vít Ondruch

WARNING: This release fixes a very old bug

• The bug relates to the use of Expectation#never in combination with other expectations on the same method.

• Please ensure you fix the relevant deprecation warnings when running against v2.6.1 before upgrading to v2.7.0.

• Previously, the following test would have passed, but now it will fail with an unexpected invocation error on the foo.bar line.

  foo = mock('foo') foo.stubs(:bar) foo.expects(:bar).never foo.bar

Commits

• cb0909e [skip ci] Update documentation for v2.7.1
• d6ba8b9 Bump version to 2.7.1 & prepare for release
• 4d4a027 Merge pull request #698 from freerange/expectation-with-improvements
• b30e443 Indicate when matcher logic is defined by block
• fed3387 Add custom matcher example to Expectatation#with docs
• 17a4856 Improve docs for Expectation#with when passed block
• 3ca865f Document argument precedence for Expectation#with
• 558d521 Add docs for Expectation#with when passed block
• 99f3f6b Document Expectation#with called multiple times
• c3b4b8e Clarify docs for Expectation#with yieldparam
• Additional commits viewable in compare view

Updates sqlite3 from 2.3.1 to 2.4.1

Release notes

Sourced from sqlite3's releases.

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

963cbf8139fef16d9b1037bd9e84c5239d0443fbd0d34cb94df173678f7e3c90  sqlite3-2.4.1-aarch64-linux-gnu.gem
b73d6d61d67e684589590e06490413988431a5eb0d248e2afd18f8fb9fc8da27  sqlite3-2.4.1-aarch64-linux-musl.gem
7b0eba380a0ddd04a7ed44be615ed0a9aa6e439ec47f0a877ee917598f41f493  sqlite3-2.4.1-arm64-darwin.gem
a62c24d66014d8de3e2a4f0bc2d5643f9c63596c4349d9c41880707065d5fe85  sqlite3-2.4.1-arm-linux-gnu.gem
cf6ea4d3b8de0fec2f48dfda02866c08528cb0625f216ae976e30239066a9c4f  sqlite3-2.4.1-arm-linux-musl.gem
e4c069ad08e77f86e5945d1765082b76c4409298bad371ab687c6ce4e546fd83  sqlite3-2.4.1.gem
5bf827fe1f301d3a1027a18035f2ccc58d732c2ce6d5e9b51e0ee5049934f108  sqlite3-2.4.1-x64-mingw-ucrt.gem
4f33d75c82aadc3cf974a6277fd7ac528edb4aee3b8fe8d765cfc2e31bebc142  sqlite3-2.4.1-x86_64-darwin.gem
9cb0e4a529487a35fd7896e237874a2fe8c300bdbed7c4b97149362a601baa37  sqlite3-2.4.1-x86_64-linux-gnu.gem
07176f8a22b3fd88f074801a3c5759d2e4c75fd183ba12c6c268e4ecce606b15  sqlite3-2.4.1-x86_64-linux-musl.gem
8d18948c87380bc23b9430acd92df538766aea9a417b77011c9f953ed684c5c9  sqlite3-2.4.1-x86-linux-gnu.gem
4374bb5605fa9b901e993a988701bdf2a85079c3f13c9953c9923f25acc25ae1  sqlite3-2.4.1-x86-linux-musl.gem

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

... (truncated)

Changelog

Sourced from sqlite3's changelog.

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

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

Commits

• 3641937 version bump to v2.4.1
• 3aeae97 Merge pull request #593 from sparklemotion/flavorjones-dep-sqlite-3.47.2
• ad0f370 dep: bump vendored sqlite to v3.47.2
• d774206 Merge pull request #592 from sparklemotion/flavorjones-handle-weakref-cleanup
• ec11e4c fix: handle the case where GC runs during fork safety checks
• 47f904e doc: document how to use extensions in a rails app
• 59c30ec ci: regenerate rdocs when version tags are pushed
• e6a62f3 doc: update doc URLs to https://sparklemotion.github.io/sqlite3-ruby
• 6141cfd ci: workflow to publish rdoc
• 6886f98 version bump to v2.4.0
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
sqlite3	[>= 2.0.a, < 2.1]

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.