Closed
Conversation
Collaborator
|
The PR title is definitely misleading as this doesn't fix anything. It is just a replacement of one action with another more popular one and no, it won't Closing as it is has no value. |
Author
|
@vbuberen Absolutely true!! I only got halfway through and, due to a lack of time, I haven't been able to continue. Thanks for closing it!! I hope to find more time and continue contributing 🚀 |
This file contains hidden or 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
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.
This pull request updates the GitHub Actions workflows for several plugins to use a different action for setting up Flutter. Specifically, it replaces the usage of
flutter-actions/setup-flutter@v4withsubosito/flutter-action@v2across multiple workflow YAML files. This change standardizes the Flutter setup process and may improve reliability or compatibility with current tooling.CI/CD Workflow Updates:
flutter-actions/setup-flutter@v4withsubosito/flutter-action@v2for setting up Flutter in.github/workflows/all_plugins.yaml,.github/workflows/android_alarm_manager_plus.yaml,.github/workflows/android_intent_plus.yaml,.github/workflows/battery_plus.yaml,.github/workflows/connectivity_plus.yaml, and.github/workflows/device_info_plus.yaml.No other workflow logic or steps were changed; only the Flutter setup action was updated. This should be a safe and straightforward improvement to CI consistency.