Create GitHub releases automatically on tagging #7042
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
5 tasks
Contributor
💯 thank you |
alamb
approved these changes
Jan 29, 2025
Contributor
alamb
left a comment
alamb
left a comment
There was a problem hiding this comment.
Thank you very much @kou
I also looked at the workflow runs on your fork
- https://github.com/kou/arrow-rs/actions/runs/13019303158/job/36316055818
- https://github.com/kou/arrow-rs/actions/runs/13019326631
And they both look great
I think we should merge this PR and I'll try it out when making the next release
Contributor
|
Thanks again @kou |
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?
Closes #7041.
Rationale for this change
In general, a release process should be automated as much as possible. It reduces maintenance costs and avoid human mistakes.
What changes are included in this PR?
Add a GitHub Actions workflow that is executed on tagging. It creates GitHub releases from existing information.
Example results on my fork:
55.0.0tag: https://github.com/kou/arrow-rs/releases/tag/55.0.0object_store_0.12.0tag: https://github.com/kou/arrow-rs/releases/tag/object_store_0.12.0Are there any user-facing changes?
No.