diff --git a/ChangeLog.d/Driver_wrapper_codegen_1.0.txt b/ChangeLog.d/Driver_wrapper_codegen_1.0.txt
new file mode 100644
index 0000000..8e97b01
--- /dev/null
+++ b/ChangeLog.d/Driver_wrapper_codegen_1.0.txt
@@ -0,0 +1,6 @@
+Features
+   * Add support for driver wrapper codegen 1.0. This autogenerates
+     the file library/psa_crypto_driver_wrappers.c. Rev 1.0 does not
+     support any additional templating. For further info on how to
+     patch into the psa_crypto_driver_wrappers.c refer
+     docs/proposed/psa-driver-wrappers-codegen-migration-guide.md
diff --git a/docs/proposed/psa-driver-wrappers-codegen-migration-guide.md b/docs/proposed/psa-driver-wrappers-codegen-migration-guide.md
index 6933aa4..4f82bed 100644
--- a/docs/proposed/psa-driver-wrappers-codegen-migration-guide.md
+++ b/docs/proposed/psa-driver-wrappers-codegen-migration-guide.md
@@ -29,4 +29,4 @@
 
 (1) psa_crypto_driver_wrappers.c will from this point on be auto generated.
 (2) The auto generation is based on the template file at scripts/data_files/driver_templates/psa_crypto_driver_wrappers.c.jinja.
-(3) So while all driver wrapper templating support is yet to come in, the library user will need to patch into the template file as needed.
+(3) So while all driver wrapper templating support is yet to come in, the library user will need to patch into the template file as needed, this could be read as replacing the template file with the current psa_crypto_driver_wrappers.c file maintained by the library user.