Skip to content

Conversation

@madsmtm
Copy link

@madsmtm madsmtm commented Oct 15, 2025

Motivation: To get #109 out. I decided to bump all crates for consistency, even though jemallocator-global doesn't have any changes.

I see that #143 exists, I agree that should be done, but I don't think it needs to be a blocker for getting the current things out?

r? @BusyJay.

Copy link
Member

@BusyJay BusyJay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We only keep align on minor version bump as cargo will automatically pick newer patch versions.

@madsmtm
Copy link
Author

madsmtm commented Oct 15, 2025

I've changed this to only bump jemalloc-sys, jemalloc-ctl and jemallocator then.

Copy link
Member

@BusyJay BusyJay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@BusyJay BusyJay merged commit df5934f into tikv:main Oct 15, 2025
10 checks passed
@madsmtm madsmtm deleted the new-release branch October 15, 2025 15:24
@madsmtm
Copy link
Author

madsmtm commented Oct 15, 2025

I think you have to actually cargo publish the release as well? There doesn't seem to be a CI step to do it.

Btw, remember to add the tags:

git tag 0.6.0 f260a80f21b7f9eb1212809720d9a5f7f0cf0e8b
git tag 0.6.1 df5934f67d7b462b431f7fe9658952178c2bf2f4
git push --tags

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants