Sometimes you may notice that an addon on Warperia has a different last update date than the date of the latest update shown in the addon’s GitHub repository.

This is because Warperia does not automatically check GitHub repositories for new addon updates.

How are GitHub addons updated on Warperia?

I manually check the supported addon repositories for new updates and upload the latest versions to Warperia. This check is normally done twice a day, although occasionally it may only be done once.

Because the process is currently manual, there can sometimes be a delay between an addon being updated on GitHub and the new version becoming available on Warperia.

For example, an addon may have been updated on GitHub on August 1, while the latest version on Warperia shows an update date of August 2 or 3. This does not mean that the addon was incorrectly updated. It simply means that the GitHub update was uploaded to Warperia later.

We currently do not have an automated system that continuously monitors all GitHub repositories for changes, but automating this process is on the roadmap.

What about the Warperia Desktop App?

The desktop app works differently.

For addons hosted on GitHub, the Warperia app can detect when a new commit is available in the repository. This allows the app to notify you when a newer version is available without waiting for the website to be manually updated.

As a result, GitHub-hosted addons can be updated through the Warperia Desktop App as soon as a new update is detected, even if the latest version has not yet been uploaded to the website.