We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This PR is an example of the dev bump workflow bot behaving poorly right after a release: 8ec8a22.
The correct move would have been to go from 2.26.0 to 2.27.0-dev.0, but the workflow mistakenly changed from 2.26.0 to 2.26.0-dev.0.
The text was updated successfully, but these errors were encountered:
another example of an incorrect bump: #6142
Sorry, something went wrong.
@kenzieschmoll The assumption is that this step is done manually as part of the release process. https://github.com/flutter/devtools/blob/master/tool/RELEASE_INSTRUCTIONS.md#update-to-the-next-version
This can be quickly done by running the command in the above step.
I can definitely add a check to make sure that nothing happens when we find ourselves in this case though.
short circuiting the workflow if we find ourself in that state sgtm
CoderDake
Successfully merging a pull request may close this issue.
This PR is an example of the dev bump workflow bot behaving poorly right after a release: 8ec8a22.
The correct move would have been to go from 2.26.0 to 2.27.0-dev.0, but the workflow mistakenly changed from 2.26.0 to 2.26.0-dev.0.
The text was updated successfully, but these errors were encountered: