feat(ci): add tag creation to our release script#3029
Merged
Conversation
t00ts
force-pushed
the
t00ts/ci-release-tags
branch
from
7b0fba4 to
83b8c74
Compare
t00ts
force-pushed
the
t00ts/ci-release-tags
branch
from
bc6dfab to
912c08f
Compare
kkovaacs
approved these changes
Sep 26, 2025
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.
The whole goal of automating tag creation was that anyone, without prior knowledge, could cut a release.
Apparently, the auto-tag feature won't work due to a Github limitation that prevents other workflows (e.g. Docker) from triggering.
So I've rolled back the auto-tag and instead added it to our release script. This preserves my initial intention of guiding anyone through the process seamlessly, while circumventing this dumb Github restriction.
🍻
See also #3028