Skip to content

Feature/bump sqlite 3.53.2 3.53.3#31

Merged
gms1 merged 3 commits into
mainfrom
feature/bump_sqlite_3.53.2_3.53.3
Jul 5, 2026
Merged

Feature/bump sqlite 3.53.2 3.53.3#31
gms1 merged 3 commits into
mainfrom
feature/bump_sqlite_3.53.2_3.53.3

Conversation

@gms1

@gms1 gms1 commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Summary by CodeRabbit

  • Bug Fixes

    • Updated the bundled SQLite version to v3.53.3.
    • Aligned build configuration with the newer SQLite release.
  • Chores

    • Refreshed several project dependencies and tooling versions.

@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@gms1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fd595d7b-ee84-43ee-a323-912d9c709501

📥 Commits

Reviewing files that changed from the base of the PR and between 8f2435f and 94e706d.

📒 Files selected for processing (9)
  • README.md
  • docs/DEVELOP.md
  • memory-bank/build-system.md
  • memory-bank/decisionLog.md
  • memory-bank/development.md
  • memory-bank/project-overview.md
  • package.json
  • tools/benchmark-drivers/README.md
  • tools/semver-check.js
📝 Walkthrough

Walkthrough

This PR bumps the bundled SQLite version from v3.53.2 to v3.53.3 (README and build config), and updates package.json dependency versions: node-addon-api, eslint, globals, and the optional node-gyp peer dependency.

Changes

Version Updates

Layer / File(s) Summary
SQLite version bump
README.md, deps/common-sqlite.gypi
Bundled SQLite version documentation and build variable updated from v3.53.2 to v3.53.3.
Dependency version bumps
package.json
node-addon-api, eslint, globals updated to newer versions, and optional node-gyp peerDependency bumped from 12.x to 13.x.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

  • gms1/node-sqlite3#24: Both PRs bump the bundled SQLite version in README.md and deps/common-sqlite.gypi in the same way.
  • gms1/node-sqlite3#28: Both PRs update the same SQLite version fields in deps/common-sqlite.gypi and README.md.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: bumping SQLite from 3.53.2 to 3.53.3.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
package.json (1)

56-56: 🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win

Align the node-gyp ranges
peerDependenciesMeta.optional only changes auto-install behavior; npm still validates the peer range, so 12.x vs 13.x can trigger install warnings/ERESOLVE and lead to different node-gyp versions across environments. Keep both entries on the same range.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 56, The package manifest has mismatched `node-gyp` peer
ranges, which can cause npm validation warnings and inconsistent installs.
Update the `peerDependencies`/`peerDependenciesMeta` entries for `node-gyp` in
package.json so they use the same version range, matching the existing
`13.x`-style range used elsewhere in the manifest.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@package.json`:
- Line 56: The package manifest has mismatched `node-gyp` peer ranges, which can
cause npm validation warnings and inconsistent installs. Update the
`peerDependencies`/`peerDependenciesMeta` entries for `node-gyp` in package.json
so they use the same version range, matching the existing `13.x`-style range
used elsewhere in the manifest.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 011f43d0-7e03-42a6-be74-d9dd82f10754

📥 Commits

Reviewing files that changed from the base of the PR and between 0c1127f and 8f2435f.

⛔ Files ignored due to path filters (3)
  • deps/sqlite-amalgamation-3530200.zip is excluded by !**/*.zip
  • deps/sqlite-amalgamation-3530300.zip is excluded by !**/*.zip
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (3)
  • README.md
  • deps/common-sqlite.gypi
  • package.json

@codecov

codecov Bot commented Jul 5, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (0c1127f) to head (94e706d).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #31   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines          344       344           
=========================================
  Hits           344       344           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gms1 gms1 force-pushed the feature/bump_sqlite_3.53.2_3.53.3 branch from 5f23238 to 94e706d Compare July 5, 2026 09:23
@gms1 gms1 merged commit 631820f into main Jul 5, 2026
30 checks passed
@gms1 gms1 deleted the feature/bump_sqlite_3.53.2_3.53.3 branch July 5, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant