Summary
I noticed that you added ExternalDependencyManager into your tagged versions.
I suppose that is because Google still hasn't bothered to create a Github package download for that.
However, I suppose most of us that are using your package are in one way or another including ExternalDependencyManager in our projects. Which means that when including your package through github url (or other means) will lead to conflict with guids.
To solve this, Can you please create a separate tags for your plugin that have ExternalDependencyManager not added ?
Motivations
Creating separate tags that does not include ExternalDependencyManager solves guid conflicts for those already including it.
Summary
I noticed that you added ExternalDependencyManager into your tagged versions.
I suppose that is because Google still hasn't bothered to create a Github package download for that.
However, I suppose most of us that are using your package are in one way or another including ExternalDependencyManager in our projects. Which means that when including your package through github url (or other means) will lead to conflict with guids.
To solve this, Can you please create a separate tags for your plugin that have ExternalDependencyManager not added ?
Motivations
Creating separate tags that does not include ExternalDependencyManager solves guid conflicts for those already including it.