Problem
When you publish a new tag or release for a module in GitHub, the new version may not automatically appear in the public Terraform Registry.
Cause
This issue can occur if the module's webhook is not configured to trigger on tag creation events or if there is a synchronization delay between GitHub and the Terraform Registry.
Solutions
There are two primary methods to resolve this issue.
Solution 1: Update Webhook Settings in GitHub
To automatically trigger the ingestion of new module versions, you must configure the module's webhook in GitHub to trigger on tag and branch creation or deletion events, in addition to standard push events.
Solution 2: Manually Resync the Module
If the new version does not appear after you confirm the webhook settings are correct, you can force a synchronization with GitHub from the Terraform Registry UI.
- Navigate to your module's page in the Terraform Registry.
- From the Manage Module dropdown menu, select Resync Module.
This process may take a few minutes to complete. Only use this option if the new version does not appear automatically, as it triggers a full resynchronization of all module versions.
Note: The Resync Module option is currently available only for modules in the public registry. A feature request exists to add this functionality for private registries in HCP Terraform and Terraform Enterprise.
Additional Information
- For more details on publishing modules, refer to the Releasing New Versions section of the Terraform documentation.
- For information on private registries, see the HCP Terraform Registry documentation.