Update changelog

hc-github-team-tf-provider-devex · hc-github-team-tf-provider-devex · commit 698af5e1f591 · 2025-04-18T19:54:53.000Z
diff --git a/.changes/2.37.0-beta.1.md b/.changes/2.37.0-beta.1.md
@@ -0,0 +1,6 @@
+## 2.37.0-beta.1 (April 18, 2025)
+
+NOTES:
+
+* This beta pre-release continues the implementation of managed resource identity, which should now be used with Terraform v1.12.0-beta2. Managed resources now can support import by identity during plan and apply workflows. Managed resources that already support import via the `schema.Resource.Importer` field still need to set an ID during import when an identity is provided. The `RequiredForImport` and `OptionalForImport` fields on the identity schema can be used to control the validation that Terraform core will apply to the import config block. ([#1463](https://github.com/hashicorp/terraform-plugin-sdk/issues/1463))
+
diff --git a/.changes/unreleased/NOTES-20250418-154446.yaml b/.changes/unreleased/NOTES-20250418-154446.yaml
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,9 @@
+## 2.37.0-beta.1 (April 18, 2025)
+
+NOTES:
+
+* This beta pre-release continues the implementation of managed resource identity, which should now be used with Terraform v1.12.0-beta2. Managed resources now can support import by identity during plan and apply workflows. Managed resources that already support import via the `schema.Resource.Importer` field still need to set an ID during import when an identity is provided. The `RequiredForImport` and `OptionalForImport` fields on the identity schema can be used to control the validation that Terraform core will apply to the import config block. ([#1463](https://github.com/hashicorp/terraform-plugin-sdk/issues/1463))
+
 ## 2.37.0-alpha.1 (March 20, 2025)
 
 NOTES:

-Original file line number
+Diff line change
@@ @@ -0,0 +1,6 @@ @@
 +## 2.37.0-beta.1 (April 18, 2025)
++
 +NOTES:
++
 +* This beta pre-release continues the implementation of managed resource identity, which should now be used with Terraform v1.12.0-beta2. Managed resources now can support import by identity during plan and apply workflows. Managed resources that already support import via the `schema.Resource.Importer` field still need to set an ID during import when an identity is provided. The `RequiredForImport` and `OptionalForImport` fields on the identity schema can be used to control the validation that Terraform core will apply to the import config block. ([#1463](https://github.com/hashicorp/terraform-plugin-sdk/issues/1463))
++