Description
You do have to be careful when publishing - the CI + testing would have seen the local version of the referenced package and not the published version.
In flutter_tools, package:native_assets_builder will pull in its pubspec.yaml defined dependency of package:native_assets_cli. However, in dartdev it will always use head of this repository, which is effectively a path dependency. (Dart uses DEPS and a custom packages file.)
Therefore, it would be useful to run the CI both against path dependencies and the pubspec defined dependencies.
As long as the test projects in the various packages have published dependencies, the tests using those projects should succeed. So we should really only have to test native_assets_builder with native_assets_cli as a path dependency.