Similar to https://github.com/sprucely-designed/mainwp-discord-notifications/issues/11 when installing from the GitHub release .zip file, the folder created in the wp-content/plugins directory includes the -v#.#.# version info. So on the first update using Git Updater (or manually), you will run into issues with the activation of the new plugin. From cursory research, I'll need to setup a build process to create the release with the version in the zip but without the version in the zipped directory that's created on install. Any input welcome on best practices here, but I'll do some more research in the coming weeks. I will update the readme with this as a known issue.
Similar to https://github.com/sprucely-designed/mainwp-discord-notifications/issues/11 when installing from the GitHub release .zip file, the folder created in the wp-content/plugins directory includes the
-v#.#.#version info. So on the first update using Git Updater (or manually), you will run into issues with the activation of the new plugin. From cursory research, I'll need to setup a build process to create the release with the version in the zip but without the version in the zipped directory that's created on install. Any input welcome on best practices here, but I'll do some more research in the coming weeks. I will update the readme with this as a known issue.