Skip to content

chore(vendor): bump SQLCipher to 4.19.0 - #15

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
bump/sqlcipher-4.19.0
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
bump/sqlcipher-4.19.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated bump from 4.15.0 to 4.19.0.

Source: https://github.com/sqlcipher/sqlcipher/releases/tag/v4.19.0

Reviewer checklist

  • CI is green on this PR
  • git diff --stat sqlite3.c sqlite3.h is dominated by amalgamation noise (no surprise touchpoints in our code)
  • CHANGELOG entry is sensible
  • Upstream release notes have no breaking API change for our binding

@github-actions
github-actions Bot force-pushed the bump/sqlcipher-4.19.0 branch from 791e79f to 64c940d Compare September 21, 2026 13:38
@github-actions
github-actions Bot force-pushed the bump/sqlcipher-4.19.0 branch from 64c940d to 3204bc0 Compare September 28, 2026 14:58
@github-actions
github-actions Bot force-pushed the bump/sqlcipher-4.19.0 branch from 3204bc0 to 1aac376 Compare October 5, 2026 15:34
@github-actions
github-actions Bot force-pushed the bump/sqlcipher-4.19.0 branch 2 times, most recently from 8975c37 to e6742a2 Compare October 19, 2026 14:21
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@github-actions
github-actions Bot force-pushed the bump/sqlcipher-4.19.0 branch from e6742a2 to c1b67a1 Compare October 26, 2026 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant