Bump version: 5.1.0 → 6.0.0

[amunra]

Summary by CodeRabbit

• Chores
  • Version bumped to 6.0.0 across all packages and components.
  • Documentation links and references updated to reflect the new version.

[coderabbitai]

Walkthrough

Version bump from 5.1.0 to 6.0.0 across project configuration, build files, C++ source code user agent, Rust package manifests, and documentation references. No functional logic or control flow changes introduced.

Changes

Cohort / File(s)	Summary
Version configuration .bumpversion.toml, CMakeLists.txt	Updated current version from 5.1.0 to 6.0.0 in both bumpversion configuration and CMake project declaration.
C++ source include/questdb/ingress/line_sender.hpp	Updated user agent string from "questdb/c++/5.1.0" to "questdb/c++/6.0.0".
Rust package manifests questdb-rs-ffi/Cargo.toml, questdb-rs/Cargo.toml	Bumped package versions from 5.1.0 to 6.0.0.
Documentation doc/SECURITY.md, questdb-rs/README.md	Updated documentation links and references from version 5.1.0 to 6.0.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

All changes are homogeneous version bumps following a consistent pattern across configuration, build, source, package, and documentation files. No complex logic, structural changes, or heterogeneous modifications requiring separate reasoning.

Poem

🐰 Hops up to 6.0, we go!
Version bumps from low to high,
Docs and configs synchronized,
Six point oh, let's celebrate the sky! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Bump version: 5.1.0 → 6.0.0" directly and accurately describes the main change across the entire changeset. The raw summary confirms that all modified files are related to a consistent version bump from 5.1.0 to 6.0.0, including .bumpversion.toml, CMakeLists.txt, Cargo.toml files, documentation references, and the user agent string. The title is concise, specific with exact version numbers, and uses clear formatting without any vague terms, emojis, or noise.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch v6.0.0

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 791b58d and a30d283.

⛔ Files ignored due to path filters (1)

• questdb-rs-ffi/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (7)

• .bumpversion.toml (1 hunks)
• CMakeLists.txt (1 hunks)
• doc/SECURITY.md (1 hunks)
• include/questdb/ingress/line_sender.hpp (1 hunks)
• questdb-rs-ffi/Cargo.toml (1 hunks)
• questdb-rs/Cargo.toml (1 hunks)
• questdb-rs/README.md (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-10-15T11:51:07.416Z

Learnt from: amunra PR: questdb/c-questdb-client#124 File: questdb-rs-ffi/Cargo.toml:4-4 Timestamp: 2025-10-15T11:51:07.416Z Learning: In the questdb/c-questdb-client repository, explicit MSRV pinning via `rust-version` field in Cargo.toml or `rust-toolchain` files is not required. The project accepts that older compilers will error out when encountering unsupported editions, and this is the preferred approach. 

Applied to files:

• questdb-rs/Cargo.toml
• questdb-rs-ffi/Cargo.toml

🧬 Code graph analysis (1)

include/questdb/ingress/line_sender.hpp (1)

questdb-rs/src/ingress/mod.rs (1)

• user_agent (912-918)

🪛 LanguageTool

questdb-rs/README.md

[grammar] ~86-~86: There might be a mistake here.
Context: ...trates array ingestion with ndarray. | | [protocol_version.rs](https://github...

(QB_NEW_EN)

⏰ 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). (9)

• GitHub Check: questdb.c-questdb-client (Building and testing on windows-msvc-2019)
• GitHub Check: questdb.c-questdb-client (Building and testing on windows-msvc-2022)
• GitHub Check: questdb.c-questdb-client (Building and testing on mac)
• GitHub Check: questdb.c-questdb-client (Building and testing on linux-nightly)
• GitHub Check: questdb.c-questdb-client (Building and testing on linux-beta)
• GitHub Check: questdb.c-questdb-client (Building and testing on linux-stable)
• GitHub Check: questdb.c-questdb-client (Building and testing on linux)
• GitHub Check: questdb.c-questdb-client (Building and testing Vs QuestDB 'master')
• GitHub Check: questdb.c-questdb-client (Building and testing cargo fmt and clippy)

🔇 Additional comments (8)

questdb-rs/Cargo.toml (1)

3-3: LGTM! Version bump is consistent.

The version update from 5.1.0 to 6.0.0 is correctly applied and aligns with the repository-wide version bump.

questdb-rs/README.md (2)

73-73: LGTM! Documentation link updated correctly.

The docs.rs link now correctly references version 6.0.0.

---

77-87: LGTM! Example links updated consistently.

All example links now correctly reference the 6.0.0 version tag in the repository.

doc/SECURITY.md (1)

38-39: LGTM! API documentation links updated correctly.

The SenderBuilder API documentation links now correctly reference version 6.0.0.

questdb-rs-ffi/Cargo.toml (1)

3-3: LGTM! FFI crate version updated correctly.

The version bump from 5.1.0 to 6.0.0 is correctly applied and consistent with the main crate.

include/questdb/ingress/line_sender.hpp (1)

1178-1178: LGTM! User agent string updated correctly.

The C++ client user agent now correctly identifies as version 6.0.0, consistent with the version bump.

.bumpversion.toml (1)

2-2: LGTM! Central version tracking updated.

The current version has been correctly updated to 6.0.0. Note that this is a major version bump (5.x → 6.x), which typically signals breaking changes according to semantic versioning conventions.

Consider verifying that:

1. This major version bump is intentional
2. Breaking changes (if any) are documented in a changelog or release notes
3. Migration guidance is provided for users upgrading from 5.x

This is good practice for major version releases to help users understand what changed.

CMakeLists.txt (1)

2-2: LGTM! CMake project version updated correctly.

The project version has been updated to 6.0.0, which will be reflected in the package version (CPACK_PROJECT_VERSION).

---

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