no available releases match the given constraints 3.0.0, ~> 2.2, ~> 2.2

[hashicorp]

no available releases match the given constraints 3.0.0, ~> 2.2, ~> 2.2

[paultyng]

I'm not sure whats wrong in this case, do you possibly have another version constraint somewhere else in your configuration, for example in a terraform block's required_providers?

When I run your sample file in a clean directory I get:

PS C:\Users\paul\sandbox\013> terraform version
Terraform v0.13.4
PS C:\Users\paul\sandbox\013> terraform init

Initializing the backend...

Initializing provider plugins...
- Finding hashicorp/random versions matching "3.0.0"...
- Installing hashicorp/random v3.0.0...
- Installed hashicorp/random v3.0.0 (signed by HashiCorp)

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

[snolan-uturn]

If your module uses another module that has a conflicting version requirement this will occur, so check the required_provider blocks in any modules referenced by your module. This is referred to in the docs here https://www.terraform.io/docs/configuration/provider-requirements.html#best-practices-for-provider-versions

[paultyng]

Yes, sorry I missed this above, this is the result of module version requirements being in conflict with each other or the root module. They need to agree on their constraints.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.