Lubinik Updater
Utility Plugin
Lubinik Updater is the private maintenance layer for Lubinik sites. It checks installed Lubinik themes and plugins against private GitHub repositories, compares local versions with stable tags, and lets an admin update packages without turning production sites into Git workspaces.
- github
- maintenance
- updater
Problem
Once Lubinik became a constellation of reusable parts, maintenance became its own problem. The parent theme, core plugin, support plugins, addons, and child themes could live across several local and production sites. Updating all of them manually through ZIP uploads, memory, and repeated checks would make the framework harder to trust over time.
Solution
The updater keeps production updates tag-based and explicit. Packages are declared in a config file with their local plugin file or theme stylesheet and their GitHub repository. The admin screen scans what is installed, reads the latest accessible tag, compares versions, and offers a manual update action when a newer tagged release exists. Private repositories use a GitHub token, and updates download the tag ZIP, create a backup under uploads, then replace the installed package directory.
Results
Lubinik now has a cleaner maintenance path for real sites. Local development can stay Git-based, while production sites can update like normal WordPress installations from private, tagged releases. The updater also made release hygiene more concrete: versions, tags, export-ignore rules, repository access, and package declarations all became part of keeping Lubinik alive without relying on memory.
