*  - If module A depends on module B and module B is being removed, in addition to the removal event for module B, module A also
     *    receives an update event.
     */
    UPDATE,

    /**
     * The [KtModule] is being removed. Because this event is published before the removal, the [KtModule] can still be accessed to clear

[verification-metadata.xml](https://github.com/JetBrains/kotlin/blob/master/gradle/verification-metadata.xml) file.

It's expected that `verification-metadata.xml` should only be updated with the commits that modify the build. There are some tips how
to perform such updates:

- Delete `components` section of `verification-metadata.xml` to avoid stockpiling of old unused dependencies. You may use the following command:
```bash
#macOS

 * affected. This allows subscribers to access the module's properties and dependencies to invalidate or update caches.
 *
 * #### Implementation Notes
 *
 * Analysis API platforms need to take care of publishing modification topics via the [analysisMessageBus]. In general, if your platform