diff --git a/docs/BuildExtensibility.md b/docs/BuildExtensibility.md
index b4542495b..2133eaa73 100644
--- a/docs/BuildExtensibility.md
+++ b/docs/BuildExtensibility.md
@@ -15,7 +15,7 @@ In the below example, when building the library `my.library` the `babel` task wi
 ````yaml
 ---
 # In this example configuration two custom tasks are defined: 'babel' and 'generateMarkdownFiles'.
-specVersion: "0.1"
+specVersion: "1.0"
 type: library
 metadata:
 	name: my.library
@@ -36,7 +36,7 @@ You can also connect multiple custom task with each other. Please be aware that
 ````yaml
 ---
 # In this example 'myCustomTask2' gets executed after 'myCustomTask1'.
-specVersion: "0.1"
+specVersion: "1.0"
 type: library
 metadata:
 	name: my.library
@@ -56,7 +56,7 @@ A custom task extension consists of a `ui5.yaml` and a [task implementation](#ta
 
 ````yaml
 ---
-specVersion: "0.1"
+specVersion: "1.0"
 kind: extension
 type: task
 metadata:
@@ -76,7 +76,7 @@ The task extension will then be automatically collected and processed during the
 ````yaml
 # ui5.yaml configuration for the above example
 
-specVersion: "0.1"
+specVersion: "1.0"
 kind: project
 type: library
 metadata:
@@ -89,7 +89,7 @@ builder:
 		color: blue
 ---
 # Task extension as part of your project
-specVersion: "0.1"
+specVersion: "1.0"
 kind: extension
 type: task
 metadata:
diff --git a/docs/Configuration.md b/docs/Configuration.md
index c7cc73eea..a08031a1d 100644
--- a/docs/Configuration.md
+++ b/docs/Configuration.md
@@ -18,7 +18,7 @@ The preferred way of storing the configuration of a UI5 Build and Development To
 **Example**
 ````yaml
 ---
-specVersion: "0.1"
+specVersion: "1.0"
 type: application
 metadata:
   name: my-application
@@ -30,7 +30,7 @@ Configuration can also be supplied by other means. In cases where JSON is used,
 
 ````yaml
 ---
-specVersion: "0.1"
+specVersion: "1.0"
 type: application|library|module
 metadata:
   name: testsuite
@@ -101,7 +101,7 @@ Also see [RFC 0002 Project Shims](https://github.com/SAP/ui5-tooling/blob/master
 
 #### Structure
 ```yaml
-specVersion: "0.1"
+specVersion: "1.0"
 kind: extension
 type: project-shim
 metadata:
@@ -109,12 +109,12 @@ metadata:
 shims:
     configurations:
         <module name (id)>:
-            specVersion: "0.1",
+            specVersion: "1.0",
             type: <project type>
             metadata:
                 name: <project name>
         <module name (id)>:
-            specVersion: "0.1",
+            specVersion: "1.0",
             type: <project type>
             metadata:
                 name: <project name>
@@ -158,12 +158,12 @@ An application "my-application" defines a npm dependency to [lodash](https://lod
 
 **ui5.yaml**
 ```yaml
-specVersion: "0.1"
+specVersion: "1.0"
 type: application
 metadata:
   name: my.application
 --- # Everything below this line could also be put into the ui5.yaml of a standalone extension module
-specVersion: "0.1"
+specVersion: "1.0"
 kind: extension
 type: project-shim
 metadata:
@@ -171,7 +171,7 @@ metadata:
 shims:
   configurations:
     lodash: # name as defined in package.json
-      specVersion: "0.1"
+      specVersion: "1.0"
       type: module # Use module type
       metadata:
         name: lodash
@@ -239,12 +239,12 @@ application-a/
 The shim defined in the application configures the legacy libraries and defines their dependencies. This shim might as well be a standalone module that is added to the applications dependencies. That would be the typical reuse scenario for shims.
 
 ```yaml
-specVersion: "0.1"
+specVersion: "1.0"
 type: application
 metadata:
     name: application.a
 ----
-specVersion: "0.1"
+specVersion: "1.0"
 kind: extension
 type: project-shim
 metadata:
@@ -252,17 +252,17 @@ metadata:
 shims:
     configurations:
         legacy-library-a:
-            specVersion: "0.1"
+            specVersion: "1.0"
             type: library
             metadata:
                 name: legacy.library.a
         legacy-library-b:
-            specVersion: "0.1"
+            specVersion: "1.0"
             type: library
             metadata:
                 name: legacy.library.b
         legacy-library-x:
-            specVersion: "0.1"
+            specVersion: "1.0"
             type: library
             metadata:
                 name: legacy.library.x