You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Repository collaborators can run the JMH benchmark suite against this PR by commenting:
/benchmark
Optional regression threshold override (Δ% on Time or Alloc/op; defaults to 10%):
/benchmark threshold=15
Only one benchmark run per PR is active at a time — issuing a new /benchmark comment cancels the previous run. After the run finishes a separate comment will be posted comparing it against the latest scheduled run on main; the PR check fails if any benchmark regresses by more than the threshold.
Summary
This is a pre-release preparation PR for the 0.10.0-rc1 milestone. It bumps the version from 0.9.8-SNAPSHOT to 0.10.0-rc1-SNAPSHOT across all Maven/Gradle modules, introduces a new VERSION file as the single source of truth for the release version, substantially expands CHANGELOG.md with breaking changes, new features, bug fixes, and deprecations, adds a migration guide at docs/releases/0_10_0.md and a floating-point precision doc for jdbc-v2. Critically, it overhauled .github/workflows/release.yml: the manual version workflow input is removed in favor of reading from the VERSION file, permissions: write-all is narrowed to permissions: contents: write, and two third-party actions (samuelmeuli/action-maven-publish@v1 and zhicwu/action-automatic-releases@latest) are replaced by direct mvn deploy and gh release create calls. The release.sh helper is updated to write the VERSION file, and a build_examples.sh script is added.
What this impacts
.github/workflows/release.yml — full release automation (Maven Central publish + GitHub release creation)
Root pom.xml and all example/performance pom.xml/gradle.properties — version string
High rule fired: "Changes to release workflow" — release.yml is substantially rewritten. The direction of the changes is positive (narrower permissions, eliminating unpinned third-party actions), but the rewrite changes how secrets are passed to Maven, how the release tag is derived, and how GitHub releases are created. Any error here silently breaks the ability to cut a release.
Unpinned actions/checkout@v4 and actions/setup-java@v4 remain; the replaced actions were also unpinned. Not a regression but worth noting.
Diff is 440 lines (just over the 400-line threshold), but the bulk is CHANGELOG text and docs rather than logic changes.
Required reviewer action
At least one human reviewer should verify the release workflow end-to-end (secret names, Maven profile, gh release create invocation, and that the new VERSION-file mechanism matches release.sh output) before merging.
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
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.
Summary
Checklist
Delete items not relevant to your PR: