I believe I pushed the SQLite 3.50.3 sources tohttps://github.com/python/cpython-source-deps/releases/tag/sqlite-3.50.3.0 properly.

I've added builds of this version tohttps://github.com/beeware/cpython-android-source-deps.

!buildbot android

🤖 New build scheduled with the buildbot fleet by@mhsmith for commitc69125d 🤖

Results will be shown at:

https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F137135%2Fmerge

The command will test the builders whose names match following regular expression:android

The builders matched are:

• aarch64 Android PR
• AMD64 Android PR

I believe I pushed the SQLite 3.50.3 sources tohttps://github.com/python/cpython-source-deps/releases/tag/sqlite-3.50.3.0 properly.

Somehow thesqlite branch head and thesqlite-3.50.3.0 tag refer to different commits that differ only inCommitDate. Other than that, either commit does the update correctly.

Oh, except that both branch from thesqlite-3.45.3.0 tag, not fromsqlite-3.49.1.0 :(

except that both branch from the sqlite-3.45.3.0 tag, not from sqlite-3.49.1.0 :(

I don't think this matters? at least not any more so than it not mattering the past few updates? All the sqlite- tags since that 3.45.3.0 one are in a similar state. Ithink this is due to people using a fork to push to initially? the commits "don't appear in this repository" which I think is GH for they're identified as being in a fork's repo? (GH repos are a unified hash namespace across all forks) A little confusing to me how github manages such a weird state of a tag in a repo who's commit claims not to be.

in my own fork i probably re-pushed my branch after fixing the commit signing after getting that setup in order to follow the instructions that wanted a signed tag. (my tag was signed regardless)

Right, the tag is an accurate representation of sqlite 3.50.3.0, the history is just messier than ideal (and I'm not sure when it started to go awry, or how). It's probably not worth trying to fix, but ideally we should try to straighten it out for the future next time around, or figure out some light automation.

The GitHub "commit doesn't exist" message seems to be just that the commit is not in the history of any named branch in the repository; see for examplehttps://github.com/python/cpython/tree/2.7 where the2.7 tag replaced the2.7 branch.

🤖 New build scheduled with the buildbot fleet by@gpshead for commit6232726 🤖

Results will be shown at:

https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F137135%2Fmerge

If you want to schedule another build, you need to add the🔨 test-with-buildbots label again.

Note,SQLite 3.50.4 is now current.

Also, thanks,@gpshead, for the code to handle more hash types in the macOS installer build. But I would prefer to separate that out as a separate PR not related to SQLite. I'll do that shortly and update this PR.

Thanks@gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

Thanks@gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14.
🐍🍒⛏🤖

Sorry,@gpshead, I could not cleanly backport this to3.11 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker 532c37695d03f84fc6d12f891d26b901ef402ac4 3.11

Sorry,@gpshead, I could not cleanly backport this to3.9 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker 532c37695d03f84fc6d12f891d26b901ef402ac4 3.9

Sorry,@gpshead, I could not cleanly backport this to3.12 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker 532c37695d03f84fc6d12f891d26b901ef402ac4 3.12

Sorry,@gpshead, I could not cleanly backport this to3.10 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker 532c37695d03f84fc6d12f891d26b901ef402ac4 3.10

Sorry,@gpshead, I could not cleanly backport this to3.13 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker 532c37695d03f84fc6d12f891d26b901ef402ac4 3.13

(actually unsure ifany backport will automatically succeed given the sbom?)

GH-137436 is a backport of this pull request to the3.14 branch.

GH-137455 is a backport of this pull request to the3.13 branch.

GH-137457 is a backport of this pull request to the3.11 branch.

GH-137458 is a backport of this pull request to the3.12 branch.

GH-137459 is a backport of this pull request to the3.10 branch.

GH-137462 is a backport of this pull request to the3.9 branch.

(actually unsure ifany backport will automatically succeed given the sbom?)

Yeah, that andandroid.py, and also some of the older branches having 3.37 or 3.40 or 3.45, and this PR trying to change 3.49 to 3.50.