Repository navigation
Advance the sqlite_zstd_vfs pin to bf84ddb3 - #42
Merged
Merged
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.
Advance the sqlite_zstd_vfs FetchContent pin from 251d7b035 to the current main, bf84ddb3 — the merge that advances sqlite_zstd_vfs's own sqlite_web_vfs pin to 2a435382. This completes the bubble-up: the release build now compiles the current VFS code, including the Catch2 and readerwriterqueue commit pins, the ThreadPool queue over-alignment removal, and the ARM yield hints in both VFS spin loops. The pin stays a full commit SHA, as with this project's other FetchContent declarations; nothing else changes.
Verified locally with a fresh FetchContent build (the fetch lands exactly on bf84ddb3, and transitively on sqlite_web_vfs 2a435382) and the core test suite.