chore(release): kzstd 0.2.1 - #88
Merged
Merged
Conversation
Maintenance release. The committed ABI dumps are byte-identical to 0.2.0, so this is a patch: zstd-jni 1.5.7-16, Kotlin 2.4.20, Gradle 9.7.1, the daemon JVM pinned to 21, snapshots off macOS, configuration cache on, and the JS test-harness CVE floors raised. All three version sources move together - VERSION, gradle.properties and the CHANGELOG section - because the release workflow now fails unless they agree, and renders the release body from that section rather than from commit titles. Claude-Session: https://claude.ai/code/session_011u5s67941BgPciWeLgb9jh
|
Warning Review limit reachedNext included review available in 27 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
First release cut through the new changelog gate (#87, #85). 23 commits have landed since
v0.2.0and none of them are described anywhere a release can read.The committed ABI dumps are byte-identical to 0.2.0 (
git diff v0.2.0..main -- '*.api'is empty across both tracked dumps), so this is a patch, not a minor.🧹 Chores
VERSION,gradle.properties:VERSION_NAMEand a new## [0.2.1]CHANGELOG section, moved together — the release workflow now fails unless all three agree, and renders the GitHub release body from that section instead of from commit titles.Contents of the release: zstd-jni 1.5.7-16 on the JVM backend, Kotlin 2.4.20, Gradle 9.7.1, the Gradle daemon JVM pinned to 21, snapshots publishing from Linux rather than macOS, the configuration cache enabled, and the JS test-harness CVE floors raised for the 2026-08-19 Dependabot alerts (test-only — nothing in the published artifacts changed).
Testing Performed
Ran the workflow's own gate locally against the edited tree:
Tagging
v0.2.1after this merges is what publishes to Maven Central.