fix: resolve pre-existing CI failures - #159
Open
AlexV525 wants to merge 1 commit into
Open
Conversation
AlexV525
force-pushed
the
fix/ci-preexisting-failures
branch
7 times, most recently
from
August 13, 2026 15:03
20fe5c3 to
65eaa51
Compare
Example deprecation warnings (flutter analyze): - Replace withOpacity() with withValues(alpha:) - Replace getSize() with getSizeResult().size - Replace ShowValueIndicator.always with .onDrag - Bump image_size_getter to ^2.4.0 for getSizeResult API Workflow modernization (reference flutter_photo_manager): - runnable.yml: inline steps instead of runnable.sh, use dart doc --dry-run, add concurrency, analyze each package directly - try-add-to-new-project.yml: replace ancient Flutter 3.0.5/3.7.0/3.10.6 matrix with stable-only, one job per platform
AlexV525
force-pushed
the
fix/ci-preexisting-failures
branch
from
August 13, 2026 15:10
65eaa51 to
b61bda5
Compare
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
1 participant
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.
Summary
Fixes all pre-existing CI failures that were independent of the SPM migration (#158).
Root causes & fixes
1.
flutter analyzedeprecation warnings → errorThe example used deprecated Flutter / package APIs that newer stable Flutter flags as
info, causingflutter analyzeto exit non-zero.Color.withOpacity(x)Color.withValues(alpha: x)ImageSizeGetter.getSize()ImageSizeGetter.getSizeResult().sizeShowValueIndicator.alwaysShowValueIndicator.onDragAlso bumped
image_size_getter: ^2.1.2 → ^2.4.0to get thegetSizeResultAPI.2. Ancient Flutter version matrix → runner incompatibility
try-add-to-new-project.ymltested against Flutter 3.0.5 / 3.7.0 / 3.10.6, which:File.exists?(removed in Ruby 3.4 on current runners)windows-latest)Fix: Rewrote to use
stableonly, one job per platform (matchingflutter_photo_managerpattern).3.
runnable.shfragilityThe shell activated
dart pub global run dartdoc(slow, version-sensitive). Replacedrunnable.ymlwith inline workflow steps: per-packageflutter analyze,dart doc --dry-run.Verification
Concurrency
Both workflows now use
concurrency: cancel-in-progress: trueto auto-cancel stale runs.Reference
CI patterns adopted from
flutter_photo_manager(runnable.yml,check-compatibility.yml).