chore: Automate GitHub Releases creation and site redirect - #497
Merged
Conversation
zeroshade
reviewed
Sep 8, 2025
| on: | ||
| push: | ||
| tags: | ||
| - "*" |
Member
Author
There was a problem hiding this comment.
I think that we don't use tags for no release use cases but let's use strict pattern.
zeroshade
approved these changes
Sep 8, 2025
zeroshade
left a comment
zeroshade
left a comment
Member
There was a problem hiding this comment.
just one nitpick. thanks for this!
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.
Rationale for this change
Fixes #496
We should automate release process as much as possible to reduce maintenance cost.
What changes are included in this PR?
v18.4.1Are these changes tested?
No...
Are there any user-facing changes?
Yes.