chore(release): prepare 0.1.0 release - #89
Merged
andygrove merged 1 commit intoMay 26, 2026
Merged
andygrove merged 1 commit into
andygrove merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
- Add `dev/changelog/0.1.0.md` generated by `dev/release/generate-changelog.py` (PR apache#88) covering the full range from the root commit to the branch-0.1 HEAD. 48 commits from 2 contributors. - Bump parent + module versions from `0.1.0-SNAPSHOT` to `0.1.0` across `pom.xml`, `core/pom.xml`, and `examples/pom.xml`. The native crate version in `native/Cargo.toml` is already 0.1.0; no change needed there.
This was referenced May 26, 2026
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.
Which issue does this PR close?
Rationale for this change
`branch-0.1` is the release branch for the 0.1.0 line. Before cutting the first RC tag we need (a) a written changelog covering everything that landed since the project was seeded, and (b) the version stripped of its `-SNAPSHOT` suffix so the published artifact's coordinates match the release tag.
What changes are included in this PR?
The native crate version in `native/Cargo.toml` is already at `0.1.0`, so no change there.
Are these changes tested?
`./mvnw -q validate` is clean on the rewritten poms (parent + both children resolve to a consistent `0.1.0` version).
`dev/release/generate-changelog.py` was end-to-end tested against the same range during the development of PR #88 (smoke-tested in that PR's description against `HEAD~3..HEAD`); the full `branch-0.1` run produced the file in this PR with no manual edits.
This PR depends on PR #88 (which adds the generator) only at run-time — the output (`dev/changelog/0.1.0.md`) is what ships here, not the generator itself. PR #88 is targeted at `main`; this PR is targeted at `branch-0.1`. They can land in either order.
Are there any user-facing changes?
The published artifact coordinates change from `org.apache.datafusion:datafusion-java:0.1.0-SNAPSHOT` to `org.apache.datafusion:datafusion-java:0.1.0`. This is the intended effect of the release.