WPUpSaga
Plugin used to connect to the WPUpSaga app from each remote site
by Toby Dawes · github.com/ten80snowboarder/wpupsaga-plugin · website
★ 0stars
0forks
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/ten80snowboarder/wpupsaga-plugin/archive/refs/heads/main.zipFrom the readme
WPUpSaga Plugin
Plugin used to connect a WordPress site to the WPUpSaga app.
Development notes
- Composer manages dependencies and autoloading.
- yahnis-elsts/plugin-update-checker is included so the public GitHub repository can drive in-plugin updates.
- The update checker follows the main branch version header instead of requiring GitHub Releases.
- readme.txt and the plugin header are the source of truth for the released version.
Packaging
The plugin is expected to ship with the vendor/ directory included so update installs work without running Composer on the target WordPress site.
Running bash scripts/package-release.sh now produces:
- dist/wpupsaga-.zip
- dist/wpupsaga.zip
Both ZIPs unpack into a top-level wpupsaga/ directory so manual installs land in /wp-content/plugins/wpupsaga instead of a GitHub source folder like wpupsaga-plugin-main.
Release workflow
1. Run php scripts/bump-version.php 0.1.4.
2. Review readme.txt, CHANGELOG.md, and wpupsaga.php.
3. Run bash scripts/package-release.sh 0.1.4.
4. Commit the updated plugin repo.
5. Create and push the matching annotated tag: git tag -a v0.1.4 -m "Release WPUpSaga plugin 0.1.4" && git push origin v0.1.4.
6. Push