*: bump 0.7.0#164
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✅ Files skipped from review due to trivial changes (6)
📝 WalkthroughWalkthroughThis PR coordinates a 0.7.0 release: crate versions and inter-crate path dependencies are bumped to 0.7.0 across the workspace, a new CHANGELOG entry for 0.7.0 is added, and README/inline documentation examples are updated to reference the new version. ChangesVersion 0.7.0 Release
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRsPoem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 `@jemalloc-sys/Cargo.toml`:
- Line 3: Update the version metadata in jemalloc-sys/Cargo.toml so the commit
hash suffix on the version string matches the current jemalloc submodule HEAD;
specifically edit the version value for the symbol `version` (currently
"0.7.0+5.3.1-0-g81034ce1f1373e37dc865038e1bc8eeecf559ce8") and replace the
trailing g... hash with the submodule commit
`2f9c6b3fdf7ecb69e691bb0334a54fb41fa8eeba`, keeping the rest of the version
string identical.
In `@jemallocator-global/src/lib.rs`:
- Line 8: The crate-level documentation comment in lib.rs currently references
the package name "jemallocator-global" which mismatches the README; update the
doc comment string in jemallocator-global/src/lib.rs to the README's canonical
name "tikv-jemallocator-global" so docs.rs and README use the same package name
(edit the top-line doc comment that currently reads `jemallocator-global =
"0.7"` to `tikv-jemallocator-global = "0.7"`).
🪄 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: e223d94a-3068-4758-a4bf-3215e1f1ce27
📒 Files selected for processing (9)
CHANGELOG.mdjemalloc-ctl/Cargo.tomljemalloc-sys/Cargo.tomljemalloc-sys/jemallocjemallocator-global/Cargo.tomljemallocator-global/README.mdjemallocator-global/src/lib.rsjemallocator/Cargo.tomljemallocator/README.md
| [package] | ||
| name = "tikv-jemalloc-sys" | ||
| version = "0.6.1+5.3.1-0-g81034ce1f1373e37dc865038e1bc8eeecf559ce8" | ||
| version = "0.7.0+5.3.1-0-g81034ce1f1373e37dc865038e1bc8eeecf559ce8" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check jemalloc submodule commit hash
cd jemalloc-sys/jemalloc
CURRENT_COMMIT=$(git rev-parse HEAD)
echo "Current jemalloc submodule commit: $CURRENT_COMMIT"
# Extract version metadata from Cargo.toml
cd ../..
VERSION_METADATA=$(grep -m1 "^version = " jemalloc-sys/Cargo.toml | sed 's/.*+//' | sed 's/".*//')
echo "Version metadata: $VERSION_METADATA"
# Check if commit hash in metadata matches submodule
if echo "$VERSION_METADATA" | grep -q "$CURRENT_COMMIT"; then
echo "✓ Version metadata matches submodule commit"
else
echo "✗ Version metadata does NOT match submodule commit"
echo " Expected metadata to contain: $CURRENT_COMMIT"
fiRepository: tikv/jemallocator
Length of output: 329
Align jemalloc-sys/Cargo.toml version metadata with current jemalloc submodule commit
jemalloc-sys/Cargo.toml (line 3) still has version = "0.7.0+5.3.1-0-g81034ce1f1373e37dc865038e1bc8eeecf559ce8", but jemalloc-sys/jemalloc HEAD is 2f9c6b3fdf7ecb69e691bb0334a54fb41fa8eeba, so the +g... metadata commit hash needs updating to match the submodule.
🤖 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 `@jemalloc-sys/Cargo.toml` at line 3, Update the version metadata in
jemalloc-sys/Cargo.toml so the commit hash suffix on the version string matches
the current jemalloc submodule HEAD; specifically edit the version value for the
symbol `version` (currently
"0.7.0+5.3.1-0-g81034ce1f1373e37dc865038e1bc8eeecf559ce8") and replace the
trailing g... hash with the submodule commit
`2f9c6b3fdf7ecb69e691bb0334a54fb41fa8eeba`, keeping the rest of the version
string identical.
There was a problem hiding this comment.
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 `@CHANGELOG.md`:
- Line 1: The release header in CHANGELOG.md ("# 0.7.0 - 2026-05-25") is
future-dated; replace the date portion with either "Unreleased" (e.g. "# 0.7.0 -
Unreleased") while the PR is open or update it to the actual publish date at
release time so chronology is correct; locate and edit the header line starting
with "# 0.7.0" to make this change.
🪄 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: 864bc25a-e044-40a9-8be4-dddb1179e69f
📒 Files selected for processing (8)
CHANGELOG.mdjemalloc-ctl/Cargo.tomljemalloc-sys/Cargo.tomljemallocator-global/Cargo.tomljemallocator-global/README.mdjemallocator-global/src/lib.rsjemallocator/Cargo.tomljemallocator/README.md
✅ Files skipped from review due to trivial changes (5)
- jemallocator/README.md
- jemallocator-global/README.md
- jemalloc-ctl/Cargo.toml
- jemallocator-global/src/lib.rs
- jemallocator/Cargo.toml
| @@ -1,3 +1,17 @@ | |||
| # 0.7.0 - 2026-05-25 | |||
There was a problem hiding this comment.
Avoid a future-dated release header before publish.
Line 1 uses 2026-05-25, while this PR was opened on 2026-05-24. If release is not actually published on May 25, 2026, this can misstate chronology. Consider using an Unreleased heading until publish day or update the date at release cut time.
🤖 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 `@CHANGELOG.md` at line 1, The release header in CHANGELOG.md ("# 0.7.0 -
2026-05-25") is future-dated; replace the date portion with either "Unreleased"
(e.g. "# 0.7.0 - Unreleased") while the PR is open or update it to the actual
publish date at release time so chronology is correct; locate and edit the
header line starting with "# 0.7.0" to make this change.
Signed-off-by: Jay Lee <busyjaylee@gmail.com>
Summary by CodeRabbit
Chores
Documentation