Skip to content

feat: Upgrade DuckDB to 1.5.3 - #659

Merged
ilyabo merged 4 commits into
mainfrom
upgrade-duckdb-to-153
May 26, 2026
Merged

ilyabo merged 4 commits into
mainfrom
upgrade-duckdb-to-153

Conversation

@ilyabo

@ilyabo ilyabo commented May 21, 2026 •

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • Chores
    • Updated @duckdb/duckdb-wasm to 1.33.1-dev55.0 across projects and examples
    • Updated Python DuckDB version constraints to newer 1.5.x ranges
    • Removed Monaco editor dependencies from the query PWA example and registered the PWA service worker
    • Simplified configuration by removing an unused dependency override in the CLI UI package

Review Change Stack

@coderabbitai

coderabbitai Bot commented May 21, 2026 •

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8e19898a-00a3-40ec-b7fa-b285aff14b2e

📥 Commits

Reviewing files that changed from the base of the PR and between af5e455 and 6a4e94d.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • packages/duckdb/package.json

📝 Walkthrough

Walkthrough

Bumps @duckdb/duckdb-wasm to 1.33.1-dev55.0 across the monorepo and examples, removes the CLI UI package.json override, removes Monaco editor dependencies and loader from Query PWA, and updates Python duckdb constraints to >=1.5.3,<1.6.0.

Changes

JavaScript/TypeScript DuckDB Updates

Layer / File(s) Summary
Workspace root and package DuckDB updates
package.json, packages/duckdb/package.json
Root pnpm.overrides and the duckdb workspace package update @duckdb/duckdb-wasm to include 1.33.1-dev55.0.
Example packages DuckDB version updates
examples/{ai-agent, ai-core, ai-rag, ai-subagents, ai, app-builder, cosmos-embedding, cosmos, layout, mosaic, nextjs, pivot, query-websocket, query}/package.json
Fourteen example packages update the @duckdb/duckdb-wasm override from 1.32.0 to 1.33.1-dev55.0.
CLI UI DuckDB override removal
apps/sqlrooms-cli-ui/package.json
Removed the overrides block that pinned @duckdb/duckdb-wasm.
Query PWA DuckDB bump and Monaco editor cleanup
examples/query-pwa/package.json, examples/query-pwa/src/main.tsx
Bumped DuckDB version in package.json, removed @sqlrooms/monaco-editor and monaco-editor from dependencies, and removed Monaco loader imports/config from the entrypoint.

Python DuckDB Version Update

Layer / File(s) Summary
Python package duckdb constraint updates
python/pyproject.toml, python/sqlrooms-cli/pyproject.toml, python/sqlrooms-server/pyproject.toml
Updated duckdb dependency ranges from >=1.4.0,<1.5.0 to >=1.5.3,<1.6.0; CLI pyproject has a minor trailing config adjustment.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

  • sqlrooms/sqlrooms#366: Coordinated @duckdb/duckdb-wasm version updates across package.json files and examples; related at the dependency-pin level.
  • sqlrooms/sqlrooms#624: Also modifies apps/sqlrooms-cli-ui/package.json handling of overrides for DuckDB.

Suggested labels

codex

Suggested reviewers

  • igorDykhta
  • dmitriy-kostianetskiy

Poem

🐰 I hopped through package pins and bumped a few,
DuckDB's new dev build jumps into view —
Examples refreshed, Monaco said goodbye,
Python constraints lifted toward the sky.
A tiny rabbit cheers this tidy review.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Upgrade DuckDB to 1.5.3' is partially related to the changeset. While the PR does upgrade DuckDB in Python dependencies, it also simultaneously upgrades DuckDB WASM to 1.33.1-dev55.0 and removes Monaco editor dependencies, making the title incomplete. Consider revising the title to be more comprehensive, such as 'Upgrade DuckDB to 1.5.3 and DuckDB WASM to 1.33.1-dev55.0, remove Monaco editor' to accurately reflect all major changes in the changeset.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch upgrade-duckdb-to-153

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 and usage tips.

@ilyabo
ilyabo marked this pull request as ready for review May 21, 2026 21:59
@ilyabo ilyabo changed the title feat: Upgrade Python DuckDB to 1.5.3 feat: Upgrade DuckDB to 1.5.3 May 21, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 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.

Inline comments:
In `@package.json`:
- Line 113: The root package.json pins the dependency "`@duckdb/duckdb-wasm`" to
the dev tag "1.33.1-dev55.0" which propagates across the workspace; either
confirm and document that this dev build is intentionally required
workspace-wide or replace the pinned dev tag with a stable/GA release (e.g.,
"1.33.1" or a caret range) everywhere it appears (root package.json, examples/**
package.json files, and packages/duckdb package.json) and then regenerate the
lockfile (run pnpm install) so pnpm-lock.yaml reflects the new specifier; update
any workspace README or package documentation to note the intentional dev pin if
you choose to keep it.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: db0fde92-287a-4979-9e42-705793f6dc4d

📥 Commits

Reviewing files that changed from the base of the PR and between 4a5f630 and af5e455.

⛔ Files ignored due to path filters (4)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
  • python/sqlrooms-cli/uv.lock is excluded by !**/*.lock
  • python/sqlrooms-server/uv.lock is excluded by !**/*.lock
  • python/uv.lock is excluded by !**/*.lock
📒 Files selected for processing (22)
  • apps/sqlrooms-cli-ui/package.json
  • examples/ai-agent/package.json
  • examples/ai-core/package.json
  • examples/ai-rag/package.json
  • examples/ai-subagents/package.json
  • examples/ai/package.json
  • examples/app-builder/package.json
  • examples/cosmos-embedding/package.json
  • examples/cosmos/package.json
  • examples/layout/package.json
  • examples/mosaic/package.json
  • examples/nextjs/package.json
  • examples/pivot/package.json
  • examples/query-pwa/package.json
  • examples/query-pwa/src/main.tsx
  • examples/query-websocket/package.json
  • examples/query/package.json
  • package.json
  • packages/duckdb/package.json
  • python/pyproject.toml
  • python/sqlrooms-cli/pyproject.toml
  • python/sqlrooms-server/pyproject.toml
💤 Files with no reviewable changes (2)
  • apps/sqlrooms-cli-ui/package.json
  • examples/query-pwa/src/main.tsx

Comment thread package.json
@ilyabo
ilyabo merged commit cc15a10 into main May 26, 2026
6 checks passed
@ilyabo
ilyabo deleted the upgrade-duckdb-to-153 branch May 26, 2026 11: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