-
Notifications
You must be signed in to change notification settings - Fork 81
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
ci: update dry run string #180
Conversation
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.
I think we should follow the approach we use in the TypeScript repository, which has 2 github actions for different branches release in the main branch. It's very easy to forget and make mistakes to have different workflows in different branches.
Opinions?
28d6dfa
to
51ea044
Compare
Hi @yuhao900914, I am taking this differently.
|
Thanks @justin-fiedler for jumping into a sync:
|
🎉 This PR is included in version 4.0.0-beta.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
A stable version release will trigger publish automatically by
Amplitude-Flutter/.github/workflows/publish.yml
Line 6 in cf63a68
To publish a beta version
flutter pub publish --dry-run
flutter pub publish