docs(ducklake): correct the embedded DuckDB version per release line

[claudespice]

Summary

The DuckLake pages claim DuckDB 1.5.3. That value is right only for the v2.0.x line; every other release line embeds a different DuckDB, and trunk embeds 1.4.4.

Cargo.toml on trunk is explicit about the mapping between the duckdb crate version and the DuckDB library version, which is what makes this checkable — the crate versions are not the DuckDB versions:

duckdb = "1.4.4" # the crate version that matches DuckDB v1.4.4
duckdb = { git = "https://github.com/spiceai/duckdb-rs.git", rev = "9d7be742…" } # branch: spiceai-1.4.4 (DuckDB v1.4.4, arrow 58; …)

Reading that comment at each release tag gives:

Release line	Tags	Embedded DuckDB	Docs said	Verdict
vNext (trunk)	—	1.4.4	1.5.3 (catalog page)	wrong
v2.2.x	v2.2.1 / v2.2.0	1.4.4 / 1.5.5	1.5.3	wrong
v2.1.x	v2.1.2–v2.1.5 / v2.1.0–v2.1.1	1.5.5 / 1.5.3	1.5.3	wrong for v2.1.2+
v2.0.x	v2.0.0 / v2.0.1	1.5.3	1.5.3	correct — left unchanged

The vNext connector page was corrected to 1.4.4 in #2186; this PR sweeps the sibling catalog page it missed, plus every versioned snapshot that carries the same claim.

What changed

• website/docs/components/catalogs/ducklake.md — 1.5.3 → 1.4.4, wording matched to the connector page docs: reconcile the docs with the runtime changes since v2.2 #2186 already fixed.
• versioned_docs/version-2.2.x/ (connector + catalog) — "Spice v2.2.1 embeds DuckDB 1.4.4; v2.2.0 embeds DuckDB 1.5.5".
• versioned_docs/version-2.1.x/ (connector + catalog) — "Spice v2.1.2 and later embed DuckDB 1.5.5; v2.1.0 and v2.1.1 embed DuckDB 1.5.3".

The version changed inside the 2.1.x and 2.2.x lines, so a single flat number is wrong for part of each line's readership — hence the per-patch wording rather than just swapping one digit.

Source refs

• Downgrade DuckDB to v1.4.4 spiceai#13742 — "Downgrade DuckDB to v1.4.4" (merged 2026-08-30, first shipped in v2.2.1, tagged 2026-09-02)
• Cargo.toml at v2.2.1 / at v2.2.0 / at v2.1.5 / at v2.1.1
• Prior maintenance of this same claim: DuckLake: update supported version section after DuckDB 1.5.2 upgrade #1732 (→1.5.2), docs(ducklake): bump bundled DuckDB version to 1.5.3 #1792 (→1.5.3)

Out of scope

The versioned pages also assert "which supports DuckLake 1.0". #2186 dropped that clause from the vNext connector page rather than restate it, and I have no runnable evidence for which DuckLake catalog version each DuckDB build accepts, so I left the clause alone on the snapshots instead of guessing.

Test plan

• cd website && npm run build passes
• Versioned-docs propagation checked: grep -rn "DuckDB 1.5.3" website/ now returns only the two v2.0.x files, which are correct
• Files updated: 5

[github-actions]

✅ Pull with Spice Passed

Passing checks:

• ✅ Title meets minimum length requirement (10 characters)
• ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
• ✅ No banned labels detected
• ✅ Has at least one assignee: claudespice

[github-actions]

🔍 Pull with Spice Failed

Passing checks:

• ✅ Title meets minimum length requirement (10 characters)
• ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
• ✅ No banned labels detected

Failed checks:

• ❌ At least one assignee is required for this pull request.

Please address these issues and update your pull request.

[github-actions]

🔍 Pull with Spice Failed

Passing checks:

• ✅ Title meets minimum length requirement (10 characters)
• ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
• ✅ No banned labels detected

Failed checks:

• ❌ At least one assignee is required for this pull request.

Please address these issues and update your pull request.

[github-actions]

🚀 deployed to https://0210e389.spiceai-org-website.pages.dev