You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
big_red_button.py should run the same tests as travis #244
Somehow we should verify that the release we're about to make will be analyzer-clean and pass the tests. This is complicated by the fact that during the release your tree is in a state where 'pub' won't be happy, of course.
Comment by abarth Friday Oct 30, 2015 at 16:41 GMT
I discussed this with @sethladd . One idea is to be able to push a "beta" or "dev" version of the packages to pub that won't be visible to the public. Then we could test them from pub and once they pass the test, we could flip the bit on the server and make them the production versions of the package.
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 flutter doctor -v and a minimal reproduction of the issue.
Activity
FlutterIssues commentedon Nov 9, 2015
Friday Oct 30, 2015 at 16:41 GMT
I discussed this with @sethladd . One idea is to be able to push a "beta" or "dev" version of the packages to pub that won't be visible to the public. Then we could test them from pub and once they pass the test, we could flip the bit on the server and make them the production versions of the package.
abarth commentedon Dec 5, 2015
We now release using git hashes. We should check Travis before publishing a given git hash.
github-actions commentedon Sep 7, 2021
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
flutter doctor -vand a minimal reproduction of the issue.