Plugins are published to npm so unless uphy is willing to share his account you won't be able to publish a new version. Instead you'd need to resubmit this as a new plugin.
You could simply fork the repo (if the licence allows) and publish under a new plugin ID. We'd mark the previous as obsolete so that only the most up to date plugin shows up.
I wonder whether we should transfer the plugin ID to you or not. If it was a widely used plugin we probably would, but in this case maybe it's not necessary?
The advantage of transferring the ID is that people would automatically get your new plugin as an update to the old one. What do you guys think?
Sorry for my little knowledge of the subject, but I understand that this plugin replaces the one created by uphy, so we should uninstall the previous one and install this PlantUML v1.2.0, is that correct? I can see both in the plugin list, I know it is like a fork plugin but I assume is an improved and updated version of the first one. Right?
Thanks for the update @marc0l92. I guess we could mark the previous version as deprecated quite soon so that user can start moving to yours.
By the way the previous version could potentially crash the app as described here. It's an issue I've tried to mitigate on application side but it seems the exception thrown by the PlantUML lib escapes whatever boundary I set. Do you know if your plugin has this issue too?
I'm not using the same library that was used by the previous plugin version.
I'm not sure what is the example that should make Joplin crash by I tried the one in the first issue comment and the one in the attached file and they are both working on windows.
I've just realised it's something that can be done relatively easily via a pull request, so would you mind giving it a try and make the old PlantUML plugin obsolete?
Hello! Thanks for a cool plugin! I'm using this often. Is there any way to integrate it with links to other notes? For example: to use name of notes in PlantUML mindmaps
Seems like it doesn't navigate to the target note. Also when Joplin tries to open a link to the target site it's doing that in the internal browser and after clicking - there's no way to go back to the notes list (only force app restart)
Try to click on the link in the rendered SVG picture: