Introduction
Problem
When publishing a new tag/release version in GitHub for a pre-existing module in the public registry, sometimes the module does not pick up the new version, despite documentation indicating that it should happen automatically.
Solutions
In order to automatically trigger ingress of new module versions, the webhook for the module must be able to trigger on tag/branch creation/deletion, in addition to standard pushes and pulls.
If your version still doesn't appear properly after updating the webhook settings in GitHub, you may force a sync with GitHub by viewing your module on the registry and clicking "Resync Module" under the "Manage Module" dropdown. This process may take a few minutes. Please only do this if you do not see the version appear, since it will cause the registry to resync all versions of your module.