fix: Fixed zpa_policy_access_rule and semver issues

zscaler · Jan 8, 2025 · 0aaa3d7 · 0aaa3d7
1 parent 75622c5
commit 0aaa3d7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -13,7 +13,7 @@
 - [PR #513](https://github.com/zscaler/terraform-provider-zpa/pull/513) -Fixed attribute `app_server_groups` on `zpa_policy_access_rule` resource to prevent innadivertent drifts during plan and apply. Issue [#512](https://github.com/zscaler/terraform-provider-zpa/pull/512)
 - [PR #513](https://github.com/zscaler/terraform-provider-zpa/pull/513) - Deprecated previous `3.331.0` version due to missconfigured semversioning hash calculation.
 
-**NOTE**  v3.331.0 and v3.332.0 was a versioning mistake due to backend issues and does not represent hundreds of new features. 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  incovenience caused."
+**NOTE**  v3.331.0 and v3.332.0 was 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  incovenience caused."
 
 ## 3.331.0 (January, 5 2025)
 

diff --git a/docs/guides/release-notes.md b/docs/guides/release-notes.md
@@ -28,7 +28,7 @@ Track all ZPA Terraform provider's releases. New resources, features, and bug fi
 - [PR #513](https://github.com/zscaler/terraform-provider-zpa/pull/513) -Fixed attribute `app_server_groups` on `zpa_policy_access_rule` resource to prevent innadivertent drifts during plan and apply. Issue [#512](https://github.com/zscaler/terraform-provider-zpa/pull/512)
 - [PR #513](https://github.com/zscaler/terraform-provider-zpa/pull/513) - Deprecated previous `3.331.0` version due to missconfigured semversioning hash calculation.
 
-**NOTE**  v3.331.0 and v3.332.0 was a versioning mistake due to backend issues and does not represent hundreds of new features. 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  incovenience caused."
+**NOTE**  v3.331.0 and v3.332.0 was 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  incovenience caused."
 
 ## 3.331.0 (January, 5 2025) - DEPRECATED