add release github workflow #36
Merged
Conversation
This file contains 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
This was referenced Jan 12, 2025
Sylensky
force-pushed
the
feature/ci-release
branch
from
46327d1 to
7dc3f5a
Compare
Sylensky
force-pushed
the
feature/ci-release
branch
from
7dc3f5a to
4ae49d7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Automate the project workflow by introducing automatic release creation when a tag is pushed to the repository.
When a tag is created with
git tag -a <tag> -m "prepare <version>"it will kick the action that builds the project and publishes the release with the binary attached to the release artifacts.As a suggestion since the tags currently provided are behind the actual firmware version some tags need to be published in advance.
I will do that once this PR and the previous PR's gets merged together with the webhooks introduction.