Repository navigation
chore(deps): update sqlite3 to v6 - #3662
Conversation
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update SQLite dependency package.json |
The sqlite3 dependency range changes to ^6.0.1. The sqlite3>node-gyp override is removed. |
Priority:
Estimated code review effort: 2 (Simple) | ~5 minutes
Change: Other
Suggested reviewers: gauthier-th
Merge Risk: 
Minimal · up to dea3d
-
The SQLite upgrade is consistent with the lockfile and supported Node versions. No concrete merge-blocking issue remains, subject to normal build and test checks.
Pre-merge checks: 
4
Finishing Touches: 💡 1
-
🛠️ Fix failing CI checks: 💡
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks the package row,
The SQLite version starts to grow.
One override hops away,
The manifest changes today.
Then carrots mark the tidy trail.
Comment @coderabbitai help to get the list of available commands.
seerr
|
||||||||||||||||||||||||||||
| Project |
seerr
|
| Branch Review |
develop
|
| Run status |
|
| Run duration | 02m 16s |
| Commit |
|
| Committer | fallenbagel |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
|
|
0
|
|
|
0
|
|
|
0
|
|
|
0
|
|
|
33
|
| View all changes introduced in this branch ↗︎ | |
Description
Moves sqlite3 to v6 and drops the node-gyp override it no longer needs. The override was added years ago so sqlite3 could build with Python 3. v6 builds with the node-gyp we already depend on and ships prebuilt binaries for every platform we publish images for. Upstream marked the sqlite3 repository as unmaintained with this release, but TypeORM still supports it and nothing changes for users. TypeORM 1.0 uses better-sqlite3 instead, and we plan to move to it with that upgrade in the next minor release.
How Has This Been Tested?
Ran the build and the unit tests, seeded a fresh database through the migrations, and started the production server against it. Signing in, the user list, page rendering, Next.js image optimisation and the TMDB image proxy all worked with no runtime errors.
Screenshots / Logs (if applicable)
Checklist:
pnpm buildpnpm i18n:extractSummary by CodeRabbit