Conversation
samsymons
reviewed
Sep 23, 2025
| ) | ||
| ) | ||
| rescue FastlaneCore::Interface::FastlaneError | ||
| UI.important("Regular release task not found. If this is an automatic bump after merging a hotfix branch, this failure is expected. Rerun this workflow from an internal release branch, providing the release task URL explicitly.") |
samsymons
approved these changes
Sep 23, 2025
Contributor
samsymons
left a comment
samsymons
left a comment
There was a problem hiding this comment.
LGTM, and the spec file changes look to cover each branch correctly - thanks for the change, this is a nice explanation!
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.
Task/Issue URL: https://app.asana.com/1/137249556945/project/1203301625297703/task/1211436304902120?focus=true
Automated internal release bump will fail when run after merging a hotfix branch. That’s because when looking up the latest release version it founds the hotfix (hotfixes also create an internal tag) and then it fails to find its corresponding release task. This change logs an extra warning message instructing the user to re-run the bump workflow manually providing all parameters manually.