Versioning issue, 3.331.0 or 3.33.10

[Willem-van-hove]

Hi ZPA, it seems like the versioning did not go as intended. The latest release was 3.331.0, my guess is it should have been 3.33.10 instead.

[willguibr]

We need more details if you are having problems.
The semantic version is correct so we can't infer what the problem is with the statement provided. Our tests show a successful download of the binary without problems as well as publication in the Terraform registry here: https://registry.terraform.io/providers/zscaler/zpa/3.331.0

terraform {
  required_providers {
    zpa = {
      version = "3.331.0"
      source  = "zscaler/zpa"
    }
  }
}

Zscaler DevRel

[shearn89]

You've jumped 298 minor versions. That's a whole lot of new features!

[enza252]

Might be worth a quick check of https://semver.org/ to understand what has gone on here.

[willguibr]

NOTE v3.331.0 and v3.332.0 were a versioning mistake due to backend issues and does not represent hundreds of new features. Either version can be safely used without concerns on breaking changes. This will be corrected in the next major version release 4.0.0 upcoming in the next few weeks. We apologize for the confusion and inconvenience caused."

Upgrade to versions v3.331.0 or v3.332.0 instead.

Zscaler DevRel

[shearn89]

You may well need to remove v3.331.0 from the Terraform registry, as it will supersede this one and any others unless that's done.

[willguibr]

@shearn89 We're aware of the problem and how to manage the versions. Terraform registry does not allow the removal of released versions.
NOTE v3.331.0 and v3.332.0 were a versioning mistake due to backend issues and does not represent hundreds of new features. Either version can be safely used without concerns on breaking changes. This will be corrected in the next major version release 4.0.0 upcoming in the next few weeks. We apologize for the confusion and inconvenience caused."

Upgrade to versions v3.331.0 or v3.332.0 instead.

Zscaler DevRel