ci: fix release workflow to support release branches #834
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
derberg
requested review from
fmvilas,
dalelane and
asyncapi-bot-eve
as code owners
smoya
approved these changes
Sep 19, 2022
This was referenced Sep 20, 2022
Closed
|
@char0n manual run is not available, and rerun will probably not pick this change. But maybe we will be able to merge googepubsub binding soon, otherwise, we will just have to do an empty PR to trigger release 🤷🏼 |
|
Kudos, SonarCloud Quality Gate passed!
|
fmvilas
approved these changes
Sep 20, 2022
|
/rtm |
|
🎉 This PR is included in version 2.5.0-next-major-spec.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.5.0-next-spec.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
Recent comments about the release from the bot were added by mistake. More details in #899 |
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.
when we changed release branches, we forgot to update the workflow that reacts to them, we forgot to change the names of branches in the config
I intentionally did not make a change like
'**-spec'to have branches named explicitly