How do you specify a module's version when publishing it to the public Terraform Module Registry?

When publishing a module to the public Terraform Module Registry, the version of the module is specified through release tags in the associated repository. Using release tags allows you to manage and publish different versions of your module effectively. When you create a release tag in a version control system, such as GitHub, it reflects the state of the module at that point in time. The Terraform Registry can then reference these tags to determine which version of the module is available for users to utilize.

This method is widely recognized because it aligns with semantic versioning practices, making it clear to users what changes they can expect between different versions. Users can roll back to previous versions easily, or adopt new ones at their discretion, depending on the stability and changes present in the latest release.

Other options do not provide a mechanism for versioning that is recognized by the Terraform Module Registry. For example, updating module documentation is important for user understanding but does not inherently manage versioning. Similarly, the Terraform cloud interface or modifying configuration files would not directly inform the registry of version changes.