Update action to publish to pub.dev #189
Closed
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
|
Hello @MoralCode, thank you for this PR, the |
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.
It seems as though the recent merge of #183 should have triggered an automatic build/publish about 10 hours ago but it looks like the workflow failed.
This may help reduce instances of people reporting issues with things that are already fixed (if this is an issue)
It looks like the current action workflow is trying to use saved oauth tokens, when there may be a much easier/better way to do this as documented by flutter themselves.
This PR introduces the changes needed on the repo side for this to work. However, I am unable to make the changes on pub.dev as I don't have access to change the necessary settings
This is mainly a forward-looking fix, so prior versions between 1.8.1 (or whatevers currently on pub.dev) and the latest tagged version will probably need to be manually released.