Conversation
Collaborator
|
Review requested:
|
Member
|
@RafaelGSS Were we not able to cherry-pick the individual update sqlite commits from main/later staging branches? |
PR-URL: nodejs#62699 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> (cherry picked from commit 17d03b5) Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
PR-URL: nodejs#63217 Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> Reviewed-By: Jithil P Ponnan <jithil@outlook.com> (cherry picked from commit a91d859) Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
Backport the SQLite session extension fix for corrupt changesets that omit old values for primary-key columns. This avoids passing NULL to sessionBindValue() while applying UPDATE changesets. Refs: https://sqlite.org/src/info/e807d4e3798efd53 Signed-off-by: junius-sec <sksch323@naver.com> PR-URL: nodejs#63525 Refs: https://hackerone.com/reports/3736889 Refs: sqlite/sqlite@b869ed6 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> (cherry picked from commit d8ac301) Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
PR-URL: nodejs#63774 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> (cherry picked from commit 7239e15) Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
PR-URL: nodejs#64180 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Gürgün Dayıoğlu <hey@gurgun.day> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> (cherry picked from commit e09891c) Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
PR-URL: nodejs#64745 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Edy Silva <edigleyssonsilva@gmail.com> (cherry picked from commit ede6d6a) Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
Member
Author
|
Yes, the six commits cherry-pick cleanly onto v22.x. I'll rework this PR to preserve the original commits. |
RafaelGSS
force-pushed
the
fix/v22-sqlite-3.53.4
branch
from
September 23, 2026 17:16
1797741 to
077d788
Compare
Member
Author
|
I'm just opening it manually instead of relying on |
This was referenced Sep 23, 2026
richardlau
approved these changes
Sep 23, 2026
trivikr
approved these changes
Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the SQLite amalgamation from 3.51.3 to 3.53.4, matching the version already used on main. This includes the upstream FTS5 bounds checks for CVE-2026-11822 and CVE-2026-11824.