Update sqlite3 → 1.7.0 (unknown)#37
Closed
depfu[bot] wants to merge 1 commit into
Closed
Conversation
Author
|
Closed in favor of #38. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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.13 → ~> 1.7.0) · Repo · Changelog
Release Notes
1.7.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 31 commits:
version bump to v1.7.0Merge pull request #448 from sparklemotion/flavorjones-dep-rcd-1.4.0dep: update to rake-compiler-dock 1.4.0 finalMerge pull request #447 from sparklemotion/flavorjones-ci-ruby-3.3.0Merge pull request #444 from sparklemotion/dependabot/bundler/ruby_memcheck-2.3.0ci: update pipelines to test with ruby 3.3.0 finalbuild(deps): update ruby_memcheck requirement from 2.2.1 to 2.3.0Merge pull request #441 from sparklemotion/flavorjones-pin-alpine-to-3.18Revert "build(deps): bump actions/download-artifact from 3 to 4"Revert "build(deps): bump actions/upload-artifact from 3 to 4"ci: pin alpine to 3.18 or earlierMerge pull request #439 from sparklemotion/dependabot/github_actions/actions/upload-artifact-4Merge pull request #438 from sparklemotion/dependabot/github_actions/actions/download-artifact-4Merge pull request #440 from sparklemotion/dependabot/bundler/rdoc-6.6.2build(deps): update rdoc requirement from 6.6.1 to 6.6.2build(deps): bump actions/upload-artifact from 3 to 4build(deps): bump actions/download-artifact from 3 to 4Merge pull request #436 from sparklemotion/flavorjones-dep-rcd-1.4.0.rc2dep: rcd to 1.4.0.rc2 which uses ruby 3.3.0-rc1Merge pull request #433 from sparklemotion/dependabot/bundler/rdoc-6.6.1build(deps): update rdoc requirement from 6.6.0 to 6.6.1doc: update CHANGELOGMerge pull request #432 from casperisfine/typed-dataConvert SQLite3::Statement objects to TypedData APIConvert SQLite3::Database objects to TypedData APIConvert SQLite3::Backup objects to TypedData APIdoc: correct ruby 2.7 EOL date in CHANGELOGMerge pull request #431 from sparklemotion/flavorjones-drop-native-ruby-27-from-gemdep: drop support for old rubiesMerge pull request #429 from sparklemotion/flavorjones-ruby-33-supportext: add experimental support for ruby 3.3Depfu 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