Depfu 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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
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.1) · Repo · Changelog
Release Notes
1.6.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 10 commits:
version bump to v1.6.1
Merge pull request #379 from sparklemotion/flavorjones-update-sqlite3-3.41.0
dep: update libsqlite3 to 3.41.0
doc: add steps to CONTRIBUTING.md for upgrading libsqlite3
Merge pull request #380 from sparklemotion/flavorjones-2023-02-22-fix-macos-build
ci: add ruby 3.2 to appveyor
ci: run the suite weekly
dev: avoid warnings from `-Wold-style-definition`
ci: ensure pkg-config is installed on macos
doc: document glibc requirements on linux platforms
Depfu 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