SQLite 3.37.0 was released on 2022-02-22: https://sqlite.org/releaselog/3_38_0.html

+1 for SQLite 3.38.0.

Steve, would you mind updating the cpython sources repo? (No hurry; let's see if a patch release surfaces first.)

https://sqlite.org/releaselog/3_38_1.html

New changeset ea786a882b9ed4261eafabad6011bc7ef3b5bf94 by Mariusz Felisiak in branch 'main':
bpo-46907: Update macOS installer to SQLite 3.38.1. (GH-31656)
https://github.com/python/cpython/commit/ea786a882b9ed4261eafabad6011bc7ef3b5bf94

New changeset a8c728b8b742fd8ca5a225f79d99014794b8fdf3 by Mariusz Felisiak in branch 'main':
bpo-46907: Update Windows installer to SQLite 3.38.1. (GH-31655)
https://github.com/python/cpython/commit/a8c728b8b742fd8ca5a225f79d99014794b8fdf3

Was there any reason/need to backport this?

I think we can hold off on deciding whether to backport until at least the next round of bugfix releases. I don't know of any pressing reason one way or the other, ATM.

Updating to SQLite 3.37 was backported because of a data corruption bug that was fixed. AFAIK, there’s nothing like that in 3.38. I would prefer waiting to see if more patch releases appear. (That was also my intent, given how many patch releases we saw with 3.35; I’ll start using the dont-merge label from now on.)

Closing this tonight, unless someone objects.

3.38.2 was released on 2022-03-26. Since the update to 3.38.1 hasn't yet been in a 3.11.0 alpha release, I'm re-open this issue.

https://sqlite.org/releaselog/3_38_2.html

Let's hold these PRs a couple of weeks in case more patch releases appear. IMO we can hold it until a week or two before the beta phase kicks in.

https://sqlite.org/src/info/336851b191fe79f0 was merged to the 3.38 branch, so we should expect 3.38.3 in the coming days.

Erlend - would you be up for write permissions on the cpython-source-deps repo so you can push the SQLite updates yourself.

As I've mentioned before, merging PRs into that repo isn't any easier than doing it directly (since you also need to check file hashes and add a tag), but doing it yourself is easier than waiting on me or Zach.

> Erlend - would you be up for write permissions on the cpython-source-deps repo so you can push the SQLite updates yourself.

Yep, I’m fine with that.

Done. Feel free to push directly to the repo, and bear in mind that changes may be reflected in any version build at any point, which is why we use tags (ahem... mostly... we've gotten it wrong before). Fourth field of the version number is our private one, so it gets incremented if we need to patch or re-release something, rather than changing the tag, unless we really do want to force change the tag.

Feel free to reach out if you have any questions. Otherwise, SQLite updates are all yours :)

Great, thanks :)