prepare release 1.4.3.0

[suketa]

Summary by CodeRabbit

• Chores
  • Updated DuckDB to version 1.4.3.0, including build configuration and version tracking updates. Release documentation prepared for deployment.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Version bump release preparation across three files: DuckDB dependency updated from 1.4.2 to 1.4.3. Changes include CHANGELOG entry, Dockerfile base image version, and Ruby gem version constant.

Changes

Cohort / File(s)	Summary
DuckDB Version Bump CHANGELOG.md, Dockerfile, lib/duckdb/version.rb	Coordinated version updates from 1.4.2 to 1.4.3: CHANGELOG adds Unreleased entry, Dockerfile updates ARG DUCKDB_VERSION, and lib/duckdb/version.rb bumps VERSION constant.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• prepare release v1.4.1.1. #987: Performs the same release-related edits across CHANGELOG, Dockerfile DUCKDB_VERSION, and lib/duckdb/version.rb.
• prepare to release 1.2.1.0 #929: Makes identical code-level changes—bumping DuckDB in Dockerfile, updating VERSION constant, and adding changelog entry.
• prepare release 1.3.1.0 #964: Same set of release-preparation changes updating CHANGELOG, Dockerfile DUCKDB_VERSION, and version constant.

Poem

🐰 Hop, hop, the version's bumped to three,
DuckDB 1.4.3 is wild and free,
Three files aligned in perfect rhyme,
A rabbit's release, right on time! 📦✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main purpose of the changeset, which is to prepare and release version 1.4.3.0 by updating version numbers across the project.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3d122f0 and 19dcddc.

⛔ Files ignored due to path filters (1)

• Gemfile.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• CHANGELOG.md
• Dockerfile
• lib/duckdb/version.rb

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: suketa
Repo: suketa/ruby-duckdb PR: 0
File: :0-0
Timestamp: 2025-01-24T22:37:32.786Z
Learning: In Ruby-DuckDB C extensions, when initializing resources like prepared statements, store them directly in the context structure instead of using temporary variables to prevent memory leaks, especially when exceptions might be thrown.

📚 Learning: 2025-01-24T22:18:24.630Z

Learnt from: suketa
Repo: suketa/ruby-duckdb PR: 0
File: :0-0
Timestamp: 2025-01-24T22:18:24.630Z
Learning: When using ruby-asan (AddressSanitizer), avoid letting DuckDB throw C++ exceptions by checking conditions (like table existence) beforehand and raising Ruby exceptions directly to prevent ASAN from intercepting the C++ exceptions.

Applied to files:

• lib/duckdb/version.rb

📚 Learning: 2025-01-24T22:37:32.786Z

Learnt from: suketa
Repo: suketa/ruby-duckdb PR: 0
File: :0-0
Timestamp: 2025-01-24T22:37:32.786Z
Learning: In Ruby-DuckDB C extensions, when initializing resources like prepared statements, store them directly in the context structure instead of using temporary variables to prevent memory leaks, especially when exceptions might be thrown.

Applied to files:

• lib/duckdb/version.rb

📚 Learning: 2025-01-26T00:37:44.001Z

Learnt from: suketa
Repo: suketa/ruby-duckdb PR: 871
File: ext/duckdb/appender.c:170-178
Timestamp: 2025-01-26T00:37:44.001Z
Learning: In ruby-duckdb's DuckDB::Appender#append_uint8, values larger than uint8 max (255) are silently truncated to maintain backward compatibility, following C's implicit truncation behavior. Range checking is intentionally omitted to avoid breaking changes.

Applied to files:

• lib/duckdb/version.rb

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (18)

• GitHub Check: test (head, 1.3.2)
• GitHub Check: test (head, 1.4.3)
• GitHub Check: test (mingw, 1.4.3)
• GitHub Check: test (mswin, 1.3.2)
• GitHub Check: test (mswin, 1.4.3)
• GitHub Check: test (ucrt, 1.4.3)
• GitHub Check: test (ucrt, 1.3.2)
• GitHub Check: test (3.3.10, 1.3.2)
• GitHub Check: test (mingw, 1.3.2)
• GitHub Check: test (3.2.9, 1.4.3)
• GitHub Check: test (3.2.9, 1.3.2)
• GitHub Check: test (3.4.8, 1.4.3)
• GitHub Check: test (3.4.8, 1.3.2)
• GitHub Check: test (3.3.10, 1.4.3)
• GitHub Check: test (head, 1.4.3)
• GitHub Check: test (4.0.0, 1.3.2)
• GitHub Check: test (3.2.9, 1.3.2)
• GitHub Check: test (3.4.8, 1.3.2)

🔇 Additional comments (3)

CHANGELOG.md (1)

6-8: LGTM! Version bump is consistent and accurate.

DuckDB 1.4.3 was released on December 9, 2025, and this CHANGELOG entry correctly documents the version bump for the ruby-duckdb gem. The format and structure are consistent with previous entries.

Dockerfile (1)

4-4: LGTM! Docker version bump aligns with the release.

The DuckDB version update in the Dockerfile correctly aligns with the CHANGELOG entry and the confirmed release version.

lib/duckdb/version.rb (1)

6-6: LGTM! Gem version correctly updated.

The version constant is correctly bumped to '1.4.3.0', consistent with the CHANGELOG entry and the project's versioning convention.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}