-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New release tag format (e.g. "1.17.0-dev.0.0") not detected by flutter tool #53688
Comments
@tvolkert did you use the |
Hmm, I'm guessing this was a manual tag |
Yep, manual tag. (for now - gonna update scripts after I've documented all the changes to the publishing) |
/cc @jonahwilliams I don't know if this is one, but I wanted to note that we need to be careful of places where the tool needs to be able to handle both the old and the new version string formats. |
Could we tag the releases with both naming schemes for now, until the update percolates everywhere? Alternatively, we need to wait up for the tool fix for now |
I'm gonna wait for the tool fix and mark 1.17.0-dev.0.0 as bad, since it's only on dev for now. |
FYI, I'm going to publish another dev release that still contains this bug despite it being TODAY, to at least ensure that our dev build is signed on MacOS. |
SGTM |
Thanks, Chris! |
also need #54217 for CP |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
NOTE: This was fixed with both #53775 and #53715, if cherry-picking the fix include both.
I suspect this is because we use a regex on git tags in the flutter tool to detect tagged releases, which the new tag does not match.
UPDATE: The problem code is:
The text was updated successfully, but these errors were encountered: