-
Notifications
You must be signed in to change notification settings - Fork 106
*: bump 0.7.0 #164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*: bump 0.7.0 #164
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| [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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 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
🤖 Prompt for AI Agents |
||
| authors = [ | ||
| "Alex Crichton <alex@alexcrichton.com>", | ||
| "Gonzalo Brito Gadeschi <gonzalobg88@gmail.com>", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Avoid a future-dated release header before publish.
Line 1 uses
2026-05-25, while this PR was opened on2026-05-24. If release is not actually published on May 25, 2026, this can misstate chronology. Consider using anUnreleasedheading until publish day or update the date at release cut time.🤖 Prompt for AI Agents