We’ve noticed this issue recently when on our CI build, the deployed plugin would not present it’s details on the UPM management page.
The issue is triggered by any package version with “/” on it.
the endpoint without “origin/” works just fine.
Might want to escape it?
You’ll want to file a ticket over at Universal Plugin Manager - Issues - Ecosystem Jira . But I’m guessing that they’ll recommend for you to use Semantic Versioning (the plugin system really likes that nowadays).
Hi @diego.ferreira, as @daniel mentioned could you raise an issue for us to help you, but note the one link you can use for all support, bug reports, inquiries, and more is Jira Service Management
-nick
