Update sqlite3 → 1.6.9 (unknown) #106
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.6.9) · Repo · Changelog
Release Notes
1.6.9
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
version bump to v1.6.9Merge pull request #426 from masamitsu-murase/support_default_transaction_modedoc: update CHANGELOG for default_transaction_modedoc: document Database.new optionsSupport default transaction mode.Merge pull request #427 from sparklemotion/flavorjones-dep-sqlite-3.44.2dep: update sqlite to v3.44.2Merge pull request #428 from sparklemotion/flavorjones-upstream-ruby-headci: test edge rubies only in upstream.ymlMerge pull request #423 from sparklemotion/dependabot/bundler/rdoc-6.6.0build(deps): update rdoc requirement from 6.5.0 to 6.6.0Merge pull request #424 from sparklemotion/dependabot/bundler/ruby_memcheck-2.2.1build(deps): update ruby_memcheck requirement from 2.2.0 to 2.2.1Depfu 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