-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Windows and MacOS installer to SQLite 3.38.4 #91063
Comments
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.) |
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. |
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. |
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 :) |
I haven't seen any signs for an upcoming release on the forum, and the 3.38 branch haven't been touched in weeks. Let's just merge gh-32147 and gh-32148 now, so we have a fresh lib for the upcoming |
Are we backporting this? Normally it needs manual backports, but I can try the tags if someone lets me know how far back it ought to go. |
I can prepare backports, if needed. |
Last time we backported an SQLite bump, it was because of a data corruption bugfix. AFAIK, there's nothing like that in SQLite 3.38, but historically there has been no consistency for how to backport these PRs. I'm fine with backporting if the release managers are :) |
From the SQLite 3.38 changelog: The JSON functions are now built-ins. It is no longer necessary to use the -DSQLITE_ENABLE_JSON1 compile-time option to enable JSON support.
Hah, I'll eat those words! 😆 The SQLite 3.38.3 release announcement just arrived in my inbox. @felixxm, if you prepare new PR's, can you also remove the now obsolete |
@erlend-aasland Will do, thanks 👍 |
FYI, I've updated the sources deps repo, so all is set for the Windows installer/PR. |
And today 3.38.4 was released. Sigh! |
Quoting an email that appeared in my inbox, some forty minutes ago:
The good news is that the new release apparently only affects the CLI, so we're good to go. Quoting the 3.38.5 changelog: Further information, quoting their news page:
|
I'm closing this issue, as the macOS and Windows installers are now updated to SQLite 3.38.4. If a relevant SQLite 3.38 patch release appears in the future, open a new issue. Thanks for the PRs, Mariusz! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: