Update sqlite3 2.9.5 → 2.9.6 (patch) - #76
Open
depfu[bot] wants to merge 1 commit into
Open
Conversation
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ sqlite3 (2.9.5 → 2.9.6) · Repo · Changelog
Release Notes
2.9.6
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 28 commits:
version bump to v2.9.6Root the aggregate argument array so GC cannot free live values (GHSA-mwm8-39rw-8826) (#733)Reject database filenames and VFS names containing NUL (#732)Raise when open_v2 or open16 is called on an open database (#729)Stop a raise inside a UDF block from deadlocking other threads (#731)Pass TEXT values containing embedded NULs to UDFs intact (#730)doc: update CHANGELOG.mdRelease aggregate instances when sqlite finishes with them (#722)Stop sqlite calling into moved Ruby objects (#723)build(deps-dev): update rubocop-minitest requirement (#727)Merge pull request #728 from sparklemotion/dependabot/github_actions/actions-332b23de0ebuild(deps): bump vmactions/freebsd-vm in the actions groupMerge pull request #725 from sparklemotion/memory-stressdep(style): bump standard, fix style offenses (#726)ping to queue CItest: introduce helpers for compactionAdd a development docker image that contains valgrindAdd SQLITE3_TEST_GC_LEVEL to the test suitebuild(deps): bump the actions group with 3 updates (#721)build(deps): bump the actions group with 2 updates (#720)Merge pull request #719 from katafrakt/close-after-failed-opentest: Make sure the close-db-on-failure branch has coverageClose connection after fialed openbuild(deps): bump the actions group with 2 updates (#718)build(deps): bump the actions group with 3 updates (#717)build(deps-dev): update rdoc requirement from 7.2.0 to 8.0.0 (#716)build(deps): bump the actions group with 2 updates (#715)build(deps): bump the actions group with 2 updates (#712)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