Rewrites to point to documentation that has been move to the Flutter wiki so that the main document is much shorter, and better matches the flutter/flutter, flutter/engine, and updated flutter/plugins CONTRIBUTING.md.
Reverts #295
The corresponding flutter/flutter changes never landed, so that package layout is unusable for now. Since 2.0 was published already, to minimize long-term confusion this uses 3.0 rather than going back to 1.0.
Tags any PR submitted that changes a pubspec.yaml as (likely) needing
publishing, to easily find things that may have been missed.
Also updates the package auto-labeling for the newly-imported
flutter_image package.
Enabling the new publishing checks was done in a PR that touched at
least one package, so didn't actually run on the whole repo, causing
post-submit breakage.
This fixes the publish errors:
- Corrects a version mismatch in fuchsia_ctl and standardizes the format
it uses for listing recent versions.
- Removes all pre-release SDK requirements now that null safety is
stable.
- Fixes a publish warning about the use of 'docs' rather than 'doc' in
pigeon.
It also fixes the test in error in bsdiff by reverting #342 and fixing
it correctly. That change was completely wrong, but CI didn't catch it
since it wasn't running any tests for third_party/packages/ yet.
Updates to better align with the current flutter/plugins tooling:
- Pulls the latest flutter_plugin_tools
- Enables the new version-check functionality
- Enables the new license-check functionality
- Switches over to the new publish check functionality
- Moves format checking to a bot that does several of the very fast
checks, leaving tests as their own bot
- Switches incremental_build.sh to use the new --run-on-changed-packages
functionality instead of the bash check_changed_packages
- Moves check_changed_packages into local_tests.sh to minimize the
chances of future new code trying to use it, as it is now legacy.
- Renames incremental_build.sh to tool_runner.sh, to better match its
current behavior/use
This applies the recent license standardization to the newly-imported
flutter_markdown to align it with the rest of the repository:
- Standardizes year as 2013
- Standardizes author as "The Flutter Authors", moving other authors
to the AUTHORS file
- Uses the exact same text format for the copyright line as in other
files
Note that the files that currently list "Quiverware" are not third-party
code, but code that was submitted to flutter/flutter_markdown through
the standard PR process with a signed CLA; the reviews just didn't catch
that it was using a non-standard author line.
- Uses the exact LICENSE file line breaking used in the other Flutter repositories
- Standardizes some slight textual variants in the license block (e.g., use of "(c)",
explicitly referencing the AUTHORS file) on the format used in the other repos.
Standardize copyright author ("The Flutter Authors") and year (2013), as was previously done in flutter/plugins.
Adds per-package AUTHORS files to ensure that published packages contain the authorship information referred to in the boilerplate (again, as in flutter/plugins).
First preparatory step in enabling the automated license format check in this repository.
- Use a specific version of the plugin tools, in preparation for
publishing an updated version out of flutter/plugins.
- Use templates the same way we do in flutter/plugins for consistency
and ease of maintenance.
- Separate some setup steps into their own script steps for better
inspectability in the UI.
- Enable build tests on stable
