GGitHubUpdate repo for 3.32 stable (#9311 )

5a7d40f8创建于 2025年5月23日历史提交

文件	最后提交记录	最后更新时间
bin	[flutter_migrate] Start command and executables (#2735) * [flutter_migrate] Start command * Sync with upstream changes * Integrate with compute and add E2E tests * E2E tests passing * Resolve hangs, add help messages * Use CommandRunner * Cleanup hooks to prevent hang * Formatting * Softer requirements on test matching to ignore order * Null safety, address minor comments * Address comments * Cleanup and logging improvements * format, normalize * Kick tests * Fix tests * Improve win test robustness * Windows perms copyall * Fix directory typo bug * takeown command in CI * Add logging for windows * windows command debug logging * Skip running on unsupported flutter versions * Add main.dart * Bots memory, dynamic flutter executable * Different temp dir * Takeown of main.dart * test adjustments * Analyzer * Increase resources to dart_unit_tests * Remove logging	3 年前
lib	[various] Add `missing_code_block_language_in_doc_comment` lint to flutter/packages. (#6473) Adds this Dartdoc-related lint to the flutter repository, in replacement of the Dartdoc warning (missingCodeBlockLanguage) because it will be deprecated and removed soon. flutter/flutter already has this lint as well. Adding to flutter/engine with https://github.com/flutter/engine/pull/51944. Lint Proposal: https://github.com/dart-lang/linter/issues/4904 Issue covering future work removing the `// ignore:`s: https://github.com/flutter/flutter/issues/157620 ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [relevant style guides] and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use `dart format`.) - [x] I signed the [CLA]. - [x] The title of the PR starts with the name of the package surrounded by square brackets, e.g. `[shared_preferences]` - [x] I [linked to at least one issue that this PR fixes] in the description above. - [x] I updated `pubspec.yaml` with an appropriate new version according to the [pub versioning philosophy], or this PR is [exempt from version changes]. - [x] I updated `CHANGELOG.md` to add a description of the change, [following repository CHANGELOG style]. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. <!-- Links --> [Contributor Guide]: https://github.com/flutter/packages/blob/main/CONTRIBUTING.md [Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene [relevant style guides]: https://github.com/flutter/packages/blob/main/CONTRIBUTING.md#style [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/wiki/Chat [linked to at least one issue that this PR fixes]: https://github.com/flutter/flutter/wiki/Tree-hygiene#overview [pub versioning philosophy]: https://dart.dev/tools/pub/versioning [exempt from version changes]: https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#version-and-changelog-updates [following repository CHANGELOG style]: https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#changelog-style [test-exempt]: https://github.com/flutter/flutter/wiki/Tree-hygiene#tests	1 年前
test	[ci] Manually roll master, set -Xmx4G (#8586) Roll Flutter from 8e2a6fc3fd2c to 892f9c13a2bb (84 revisions) https://github.com/flutter/flutter/compare/8e2a6fc3fd2c...892f9c13a2bb ## Additional changes * Sets `-Xmx4G` across the repo. ## Issues Completes: https://github.com/flutter/packages/pull/8585	1 年前
.gitignore	Initialize `flutter_migrate` package (#2586)	3 年前
AUTHORS	Initialize `flutter_migrate` package (#2586)	3 年前
CHANGELOG.md	Update repo for 3.32 stable (#9311) Does all of the steps from https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md for the 3.32 stable release (except the first one, as the stable roller has already landed).	1 年前
LICENSE	Initialize `flutter_migrate` package (#2586)	3 年前
README.md	[flutter_migrate] Start command and executables (#2735) * [flutter_migrate] Start command * Sync with upstream changes * Integrate with compute and add E2E tests * E2E tests passing * Resolve hangs, add help messages * Use CommandRunner * Cleanup hooks to prevent hang * Formatting * Softer requirements on test matching to ignore order * Null safety, address minor comments * Address comments * Cleanup and logging improvements * format, normalize * Kick tests * Fix tests * Improve win test robustness * Windows perms copyall * Fix directory typo bug * takeown command in CI * Add logging for windows * windows command debug logging * Skip running on unsupported flutter versions * Add main.dart * Bots memory, dynamic flutter executable * Different temp dir * Takeown of main.dart * test adjustments * Analyzer * Increase resources to dart_unit_tests * Remove logging	3 年前
analysis_options.yaml	[flutter_migrate] base boilerplate files (#2694)	3 年前
dart_test.yaml	[ci] Add a web version of Dart unit tests (#4352) Adds new LUCI targets in bringup mode to run all possible Dart unit tests in Chrome. This is a new test (see linked issue), not a port of a Cirrus test, so it involves changes to tooling and packages: - The tooling now accepts an explicit platform. The default behavior if none is provided is the previous behavior of running in VM for everything but web plugin implementations (since that's convenient locally). - The tooling now has a basic understanding of `dart_test.yaml` `test_on` directives, to know when to skip. - Packages that don't support web have opt-out files. - Packages that do support web but have a few tests that fail on web have those tests opted out. - Packages that do support web but have a lot of failures on web have temporary opt-out files with TODOs + issue links. Most of https://github.com/flutter/flutter/issues/128979	2 年前
pubspec.yaml	Update repo for 3.32 stable (#9311) Does all of the steps from https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md for the 3.32 stable release (except the first one, as the stable roller has already landed).	1 年前

Flutter Migrate

Overview

This is a tool that helps migrate legacy Flutter projects generated with old version of Flutter to modern Flutter templates. This allows old apps to access new features, update key dependenices and prevent slow bitrot of projects over time without domain knowledge of individual platforms like Android and iOS.

Prerequisites

This tool supports migrating apps generated with Flutter 1.0.0 and newer. However, projects generated with older versions of Flutter (beta, alpha, etc) may still be compatible with this tool, but results may vary and official support will not be provided.

Projects that contain heavy modifications to the project's platform directories (eg, android/, ios/, linux/) may result in many conflicts.

Currently, only full Flutter apps are supported. This tool will not work properly with plugins, or add-to-app Flutter apps.

The project must be a git repository with no uncommitted changes. Git is used to revert any migrations that are broken.

Usage

To run the tool enter the root directory of your flutter project and run:

dart run <path_to_flutter_migrate_package>/bin/flutter_migrate.dart <subcommand> [parameters]

The core subcommand sequence to use is start, apply.

start will generate a migration that will be staged in the migration_staging_directory in your project home. This command may take some time to complete depending on network speed. The generated migration may have conflicts that should be manually resolved or resolved with the resolve-conflicts subcommand.
apply will apply staged changes to the actual project. Any merge conflicts should be resolved in the staging directory before applying

These additional commands help you manage and navigate the migration:

status Prints the diffs of the staged changes as well as a list of the files with changes. Any files with conflicts will also be highlighted.
abandon Abandons the existing migration by deleting the staging directory.
resolve-conflicts Wizard that assists in resolving routine conflicts. The wizard will routinely show each conflict where the option to keep the old code, new code, or skip and resolve manually are presented.