Giuseppe Mazzapica
1. Have a thing like `%%VERSION%%` in: plugin headers, README.txt|md, package.json, and in the main plugin file have a constant `define('MYPLUGIN_VERSION', '%%VERSION%%')`
2. Have a GitHub action triggered on tag push that replaces the version before deployment, see https://gist.github.com/gmazzap/ed7a305d55adc7e0238fffa6d66b829d
- Have code like this to simplify development using the non-built version: see https://3v4l.org/YaGJg
Disclaimer: none of the code shared above is tested :)
Giuseppe Mazzapica
@kraftner @pfefferle Also mind multisite. When plugins are installed network-wide, the upgrade/installation process might be seen on only one site (the first hit), but options are site-specific.
So, really, the best option is to check if what you expect is there with a simple flag, and if not, do it, then set the flag.
Captivated by WordPress development during his architecture studies, Giuseppe couldn't escape the web dev industry for the next two decades.WP expert and eager open source contributor, he used to say he spoke PHP better than English.Despite his undiminished interest in software development and architecture, his job has lately been more about engineering leadership and strategy than code.These days, he's struggling more with the "socio-" part of his socio-technical job.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.