Good question. In the meantime, you can add an update process to your plugins to ensure your updates are found before the plugin directory is launched. Some of us are using the f(x) Updater and some are using the GitHub Updater.
This plugin installs on a server that acts like a repository.
On this server you have to configure the plugins you want to work with.
Then you have to include a class in every plugin/theme you want to work with.
Full self-hosting solutions.
support themes and plugins.
Setup will take some time (not too much perhaps).
You have to mantain your own repository (bandwidth usage, …) if you choose to host your plugin packages on your own site.
This plugin taked care of the update process for plugins that have a line
in their header. Just add GitHub Plugin URI: user/repo
to your plugin and GitHub Updater will take care og keeping up-to-date it.
For this update to work, people that installs yout plugin must install even GitHub Updater.
10 seconds setup.
Support themes, plugins and language packs.
Works with GitHub, Bitbucket, GitLab, or Gitea.
Must be installed by your plugin users.
Checking against latest GitHub release by yourself
This is a function I se to do a simple check.
It return false if you are up-to-date, otherwise true.
Works with releases.
If you are hosting your plugin packages on your own site (ie through the media library) then you will have bandwidth usage. If you use a remote URL for the update package, there’s zero bandwidth consumption. To clarify: it works with any remote URL; you’re not limited to GitHub and the others.