SQLite amalgamation builds

sqlite/sqlite (the GitHub mirror of the canonical Fossil repository) has a tag for every release but publishes no amalgamation (sqlite3.c / sqlite3.h), and sqlite.org/download.html only hosts the current versions — no historical files.

This repository builds the amalgamation for any upstream tag with GitHub Actions and publishes it as a release here.

Cutting a release

1. Put the upstream tag into SQLITE_TAG, e.g. version-3.53.3.

2. Commit, tag the commit with the same name, and push both:

   git commit -am "SQLite 3.53.3"
   git tag version-3.53.3
   git push origin HEAD version-3.53.3

The amalgamation workflow then clones sqlite/sqlite at that tag, runs ./configure && make sqlite3.c shell.c, and creates a release for the pushed tag with these assets:

• sqlite-amalgamation-<N>.zip — same layout as the sqlite.org download (sqlite3.c, sqlite3.h, shell.c, sqlite3ext.h), with <N> encoded the same way (3.53.3 → 3530300)
• the same four files attached individually
• sha256sums.txt

The workflow fails if the pushed tag does not match the contents of SQLITE_TAG, so a stale file can't produce a mislabeled release.

Backfilling historical versions

To build an old version without making a commit, run the workflow manually (Actions → amalgamation → Run workflow) and enter the upstream tag, or:

gh workflow run amalgamation -f sqlite_tag=version-3.47.2

This creates the release (and its git tag in this repo) automatically.