chore: [branch-1.0] change version from 1.0.0-SNAPSHOT to 1.0.0 - #5105
Merged
Conversation
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
2 participants
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?
N/A - this is a release process step for the 1.0.0 release.
Rationale for this change
The release process requires that the Maven version on the release branch is changed from
1.0.0-SNAPSHOTto1.0.0before the release candidate is tagged, so that the staged Maven artifacts and the source tarball carry the final release version.What changes are included in this PR?
1.0.0-SNAPSHOTto1.0.0inpom.xml,common/pom.xml,spark/pom.xml, andspark-integration/pom.xml.comet.versionin the Spark test diffs (dev/diffs/3.4.3.diff,3.5.8.diff,4.0.2.diff,4.1.2.diff).cometversion in the Iceberg diffs (dev/diffs/iceberg/1.8.1.diff,1.9.1.diff,1.10.0.diff,1.11.0.diff).The Rust crate versions are already
1.0.0and do not need to change.How are these changes tested?
Existing CI. The Spark SQL and Iceberg test workflows apply the updated diffs and build against the new version, so they cover the version references in both the poms and the diff files.