github/flutter
7
0
Fork 0
mirror of https://github.com/flutter/flutter.git synced 2025-06-03 00:51:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update some places that mentioned the old update-packages --upgrade (#12218)

Browse Source
This commit is contained in:
Ian Hickson 2017-09-23 22:23:09 -07:00 committed by GitHub
parent ebffe15994
commit 36e7138e4f
5 changed files with 23 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTING.md
View File

@ -71,10 +71,10 @@ own code by mimicking the `pubspec.yaml` files in the `examples` subdirectories.
Running the analyzer Running the analyzer
-------------------- --------------------
When editing Flutter code, it's important to check the code with the analyzer. There are two When editing Flutter code, it's important to check the code with the
main ways to run it. In either case you will want to run `flutter update-packages --upgrade` analyzer. There are two main ways to run it. In either case you will
first, or you will get version conflict issues or bogus error messages about core clases like want to run `flutter update-packages` first, or you will get bogus
Offset from `dart:ui`. error messages about core classes like Offset from `dart:ui`.
For a one-off, use `flutter analyze --flutter-repo`. This uses the `analysis_options_repo.yaml` file For a one-off, use `flutter analyze --flutter-repo`. This uses the `analysis_options_repo.yaml` file
at the root of the repository for its configuration. at the root of the repository for its configuration.

3
packages/flutter/pubspec.yaml
View File

@ -5,9 +5,10 @@ description: A framework for writing Flutter applications
homepage: http://flutter.io homepage: http://flutter.io
dependencies: dependencies:
# To update these, use "flutter update-packages --force-upgrade".
collection: 1.14.3 collection: 1.14.3
http: 0.11.3+14 http: 0.11.3+14
intl: 0.15.1 intl: 0.15.1 # TODO(ianh): remove this, see https://github.com/flutter/flutter/issues/12050
meta: 1.1.1 meta: 1.1.1
typed_data: 1.1.4 typed_data: 1.1.4
vector_math: 2.0.5 vector_math: 2.0.5

11
packages/flutter_test/pubspec.yaml
View File

@ -1,12 +1,11 @@
name: flutter_test name: flutter_test
version: 0.0.14-dev version: 0.0.14-dev
dependencies: dependencies:
# The flutter tools depend on very specific internal implementation # To update these, use "flutter update-packages --force-upgrade".
# details of the 'test' package, which change between versions, so
# here we pin it precisely to avoid version skew across our # We depend on very specific internal implementation details of the
# packages. When changing this, also update the pubspec.yaml files # 'test' package, which change between versions, so when upgrading
# for the flutter_tools and devicelab packages. All other packages # this, make sure the tests are still running correctly.
# should depend on this one to transitively get the pinned version.
test: 0.12.24+2 test: 0.12.24+2
# We use FakeAsync and other testing utilities. # We use FakeAsync and other testing utilities.

9
packages/flutter_tools/lib/src/commands/analyze_base.dart
View File

@ -182,12 +182,15 @@ class PackageDependencyTracker {
message.writeln('Make sure you have run "pub upgrade" in all the directories mentioned above.'); message.writeln('Make sure you have run "pub upgrade" in all the directories mentioned above.');
if (dependencies.hasConflictsAffectingFlutterRepo) { if (dependencies.hasConflictsAffectingFlutterRepo) {
message.writeln( message.writeln(
'For packages in the flutter repository, try using ' 'For packages in the flutter repository, try using "flutter update-packages" to do all of them at once.\n'
'"flutter update-packages --upgrade" to do all of them at once.'); 'If you need to actually upgrade them, consider "flutter update-packages --force-upgrade". '
'(This will update your pubspec.yaml files as well, so you may wish to do this on a separate branch.)'
);
} }
message.write( message.write(
'If this does not help, to track down the conflict you can use ' 'If this does not help, to track down the conflict you can use '
'"pub deps --style=list" and "pub upgrade --verbosity=solver" in the affected directories.'); '"pub deps --style=list" and "pub upgrade --verbosity=solver" in the affected directories.'
);
throwToolExit(message.toString()); throwToolExit(message.toString());
} }
} }

12
packages/flutter_tools/pubspec.yaml
View File

@ -7,6 +7,7 @@ environment:
sdk: '>=1.19.0 <2.0.0' sdk: '>=1.19.0 <2.0.0'
dependencies: dependencies:
# To update these, use "flutter update-packages --force-upgrade".
archive: 1.0.31 archive: 1.0.31
args: 0.13.7 args: 0.13.7
cli_util: 0.1.2+1 cli_util: 0.1.2+1
@ -34,16 +35,13 @@ dependencies:
yaml: 2.1.12 yaml: 2.1.12
# We depend on very specific internal implementation details of the # We depend on very specific internal implementation details of the
# 'test' package, which change between versions, so here we pin it # 'test' package, which change between versions, so when upgrading
# precisely. When changing this, also update the pubspec.yaml files # this, make sure the tests are still running correctly.
# for the flutter_test and devicelab packages. All other packages
# should depend on flutter_test to transitively get the pinned
# version.
test: 0.12.24+2 test: 0.12.24+2
# Version from the vended Dart SDK as defined in `dependency_overrides`. # Version from the vended Dart SDK as defined in `dependency_overrides`.
analyzer: 0.31.0-alpha.0 analyzer: any
front_end: 0.1.0-alpha.5 front_end: any
dev_dependencies: dev_dependencies:
collection: 1.14.3 collection: 1.14.3