Enable --explicit-package-dependencies by default.#160289
Enable --explicit-package-dependencies by default.#160289auto-submit[bot] merged 23 commits intoflutter:masterfrom
--explicit-package-dependencies by default.#160289Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
Required for Flutter master channel to enable `explicit-package-dependencies` (flutter/flutter#160289, flutter/flutter#160257).
Smoke testing <flutter/flutter#160289> early.
08b3efc to
a974afa
Compare
…kage-dependencies
|
Hmm looks like there's still lockfile issues? |
77037c9 to
2548fc5
Compare
Trying again after #161635. |
Closes #160257.
This will sit on CI for a bit and give me a better idea of how much work there is to do.Done!IMPORTANT: Do not revert on 1-2 isolated post-submit failures.
While I've spent the last several weeks getting this passing all presubmit tests, and some integration tests I suspected might be affected, it is possible that there are 1-2 integration tests that will fail as a result of landing this PR. I'll disable the flag (
--no-explicit-package-dependencies) if the failures look obvious enough, otherwise I'll revert.