Skip to content

lib/sqlite: Upgrade from 3.40.1 to 3.53.1 - #12

Open
RaduAndreiTudorica wants to merge 1 commit into
unikraft:stagingfrom
RaduAndreiTudorica:update-sqlite-3.53.1
Open

lib/sqlite: Upgrade from 3.40.1 to 3.53.1#12
RaduAndreiTudorica wants to merge 1 commit into
unikraft:stagingfrom
RaduAndreiTudorica:update-sqlite-3.53.1

Conversation

@RaduAndreiTudorica

Copy link
Copy Markdown

This PR updates SQLite from 3.40.1 to 3.53.1 (latest stable from sqlite.org).

Changes:

  • Library.uk: version, sha256, and URL updated
  • Makefile.uk: LIBSQLITE_VERSION and LIBSQLITE_URL updated

Tested with catalog-core/sqlite on Unikraft stable (RELEASE-0.21.0 Ijiraq):

  • Build succeeds
  • Unikernel boots and runs correctly
  • SELECT query returns expected results (10 albums from chinook.db)

Signed-off-by: Radu Andrei Tudorica raduandreitudorica3@gmail.com

@RaduAndreiTudorica
RaduAndreiTudorica changed the base branch from staging to stable June 2, 2026 15:16
@RaduAndreiTudorica
RaduAndreiTudorica changed the base branch from stable to staging June 10, 2026 09:33

@StefanJum StefanJum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything works fine @RaduAndreiTudorica , thanks.
Same as in the other prs, please redo the commit, and add a commit message, similar to what you have in the PR description. Other than that it looks ok

Bump SQLite from 3.40.1 to 3.53.1, the latest release.

Update the version, the checksum, and the year in the download URL:
sqlite.org groups the amalgamation archives by release year, so the
path moves from 2022/ to 2026/. Library.uk is updated to match.

The port carries no patches and the amalgamation layout is unchanged,
so nothing else needed adjusting.

Tested on qemu/x86_64 with catalog-core/sqlite: the unikernel builds,
boots and answers queries against the bundled database, with
sqlite_version() reporting 3.53.1.

Signed-off-by: Radu Andrei Tudorica <raduandreitudorica3@gmail.com>
@RaduAndreiTudorica

Copy link
Copy Markdown
Author

Everything works fine @RaduAndreiTudorica , thanks. Same as in the other prs, please redo the commit, and add a commit message, similar to what you have in the PR description. Other than that it looks ok

Done, thanks,
rewrote the commit message with the details from the PR
description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants