-
Notifications
You must be signed in to change notification settings - Fork 495
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
Automating the publish of flutter package on pub.dev #124
Conversation
|
||
# TODO: https://github.com/microsoft/fluentui-system-icons/issues/34 | ||
# - name: Build Flutter library | ||
# uses: ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should run the flutter build
command here to ensure the library builds without failure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the dry run script to make sure that package is built properly but not publish. Let me know what you think about that :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, but for dry run, does it need the accessToken and refreshToken? Could we remove them if possible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems accessToken and refreshToken are required for the dry-run . Just tested without that and it failed.
Can you fill out the PR description? Thanks. |
The purpose of this PR is to automatically publish the fluent ui package on pub.dev whenever a new version is available. This will solve the problem where our flutter users weren't getting the latest icons. With this PR in , they will have always have the latest package.
We perform a dry-run whenever a PR is pushed which is basically creating the package and make sure nothing breaks on the branch. The actual publishing happens when the PR is merged into master.