-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
cp: approvedApproved cherry-pick requestApproved cherry-pick requestcp: merge-to-stableCherry-picks that should be merged to stableCherry-picks that should be merged to stablecp: mergedCherry-pick has been merged to the release branch.Cherry-pick has been merged to the release branch.cp: reviewCherry-picks in the review queueCherry-picks in the review queue
Description
Issue Link
Commit Hash
Target
stable
PR Link
Changelog Description
This fixes a regression to flutter upgrade that would result in an error stating "Unknown Flutter tag" unless either the user's current working directory or they run with the --force flag.
Impacted Users
All Flutter developers upgrading their SDK via flutter upgrade.
Impact Description
Users issuing flutter upgrade on any 3.13 (3.14 releases are also affected, but will be hotfixed independently) release between beta 3.13.0-0.1.pre and stable 3.13.2 (hopefully this hotfix will make it into 3.13.3) will get an error.
Workaround
Use flutter upgrade --force or change your working directory to your Flutter SDK checkout before running flutter upgrade.
Risk
medium
Test Coverage
yes
Validation Steps
once this fix is on stable:
- commit an empty commit
git commit --allow-empty -m 'empty commit' - reset to the previous commit
git reset --hard HEAD~1 - change to a directory NOT within the Flutter SDK
cd $HOME - run
flutter upgrade. This should succeed if the fix works.
Metadata
Metadata
Assignees
Labels
cp: approvedApproved cherry-pick requestApproved cherry-pick requestcp: merge-to-stableCherry-picks that should be merged to stableCherry-picks that should be merged to stablecp: mergedCherry-pick has been merged to the release branch.Cherry-pick has been merged to the release branch.cp: reviewCherry-picks in the review queueCherry-picks in the review queue