build: add GitHub fallback for SQLite source archive - #3
Closed
marcus-pousette wants to merge 1 commit into
Closed
Conversation
marcus-pousette
force-pushed
the
codex/ci-sqlite-fetch-fallback
branch
from
July 15, 2026 06:34
3b3fe0c to
5429cdb
Compare
Owner
Author
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.
Why
The primary sqlite.org release archive has intermittently returned 503 errors in CI. A matching GitHub release-tag archive gives the build a deterministic fallback without changing the SQLite source version.
What changed
sqlite-src-3530000.ziparchive first.version-3.53.0tag archive.Stack
This PR is based on #4, which synchronizes the fork with upstream wa-sqlite 1.1.1. #2 then adds the failed-open cleanup on top.
Verification
Merge method
Use Create a merge commit after #4. The dependent submodule stack refers to this exact commit ancestry.