Update README, CHANGELOG

Author: shaldengeki

CHANGELOG.md

@@ -118,6 +118,9 @@ END_UNRELEASED_TEMPLATE
   Gazelle generates `py_proto_library` rules for `proto_library`. `false` by default.
 * (gazelle) New directive `gazelle:python_proto_naming_convention`; controls
   naming of `py_proto_library` rules.
+* (gazelle) Gazelle now resolves dependencies for `py_proto_library`
+  module-level imports, i.e. `import some.package.foo_pb2`. Imports of
+  messages/enums/services inside modules are not yet supported.
 
 {#v0-0-0-removed}
 ### Removed

gazelle/README.md

@@ -288,7 +288,7 @@ py_proto_library(
 
 The default naming convention is `$proto_name$_pb2_py`, so by default in the above example Gazelle would generate `foo_pb2_py`. Any pre-existing rules are left in place and not renamed.
 
-Note that the Python library will always be imported as `foo_pb2` in Python code, regardless of the naming convention. Also note that Gazelle is currently not able to map said imports, e.g. `import foo_pb2`, to fill in `py_proto_library` targets as dependencies of other rules. See [this issue](https://github.com/bazel-contrib/rules_python/issues/1703).
+Note that the Python library will always be imported as `foo_pb2` in Python code, regardless of the naming convention.
 
 #### Directive: `python_default_visibility`: