Create GitHub releases automatically on tagging#797
Open
alamb wants to merge 1 commit into
Open
Conversation
alamb
commented
Jul 9, 2026
| # specific language governing permissions and limitations | ||
| # under the License. | ||
|
|
||
| # Creates a github release on https://github.com/apache/arrow-rs-object-store/releases |
Contributor
Author
There was a problem hiding this comment.
|
|
||
| Congratulations! The release is now official! | ||
|
|
||
| ### Check the GitHub release |
Contributor
Author
There was a problem hiding this comment.
alamb
added
the
development-process
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?
Follow-on to
Rationale for this change
This does the same thing as @kou did in apache/arrow-rs#7042 for arrow-rs-object-store: it creates GitHub Releases automatically when release tags are pushed.
This should be used with the RC-tag release flow from #796, so only the final post-approval
v<version>tag creates a GitHub Release.What changes are included in this PR?
I think we will have to test this live when the next final release tag is pushed.
Are there any user-facing changes?
No crate API or runtime behavior changes.
This adds release-manager-facing automation so final GitHub Releases are created automatically after approved release tags are pushed.