Bump model version to 1.0

docs/source/conf.py

@@ -51,8 +51,8 @@
 # These versions as replacement for |version| and |release| in rst files,
 # and are used in various other places throughout the built documents.
 #
-version = u'0.5.0'   # The short X.Y.Z version.
-release = u'0.5.0'   # The full version, including alpha/beta/rc tags.
+version = u'1.0'   # The short X.Y version.
+release = u'1.0'   # The full version, including alpha/beta/rc tags.
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

docs/source/guides/style-guide.rst

@@ -19,7 +19,7 @@ Smithy models SHOULD resemble the following example:
 
 .. code-block:: smithy
 
-    $version: "0.5.0"
+    $version: "1.0"
 
     metadata validators = []
     metadata suppressions = []

docs/source/quickstart.rst

@@ -120,7 +120,7 @@ weather service.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "example.weather#Weather": {
                     "type": "service",
@@ -175,7 +175,7 @@ identifiers, operations, and any number of child resources.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "example.weather#Weather": {
                     "type": "service",
@@ -241,7 +241,7 @@ Each ``City`` has a single ``Forecast``. This can be defined by adding the
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "example.weather#City": {
                     "type": "resource",
@@ -350,7 +350,7 @@ Let's define the operation used to "read" a ``City``.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "example.weather#GetCity": {
                     "type": "operation",
@@ -500,7 +500,7 @@ cities, so there's no way we could provide a ``City`` identifier.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "example.weather#Weather": {
                     "type": "service",
@@ -642,7 +642,7 @@ service.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "example.weather#Weather": {
                     "type": "service",
@@ -836,7 +836,7 @@ Complete example
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "example.weather#Weather": {
                     "type": "service",

docs/source/spec/amazon-apigateway.rst

@@ -62,7 +62,7 @@ The following example sets the ``X-API-Key`` header as the API key source.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#Weather": {
                     "type": "service",
@@ -294,7 +294,7 @@ Then following example enables request validation on a service:
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#Weather": {
                     "type": "service",
@@ -421,7 +421,7 @@ operation within the service.
 .. code-block:: json
 
     {
-        "smithy": "0.5.0",
+        "smithy": "1.0",
         "shapes": {
             "smithy.example#Weather": {
                 "type": "service",
@@ -532,7 +532,7 @@ The following example defines an operation that uses a mock integration.
 .. code-block:: json
 
     {
-        "smithy": "0.5.0",
+        "smithy": "1.0",
         "shapes": {
             "smithy.example#MyOperation": {
                 "type": "operation",

docs/source/spec/aws-auth.rst

@@ -60,7 +60,7 @@ Trait value
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "aws.fooBaz#FooBaz": {
                     "type": "service",
@@ -116,7 +116,7 @@ operation MUST NOT be used as part of the request signature calculation:
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#PutThings": {
                     "type": "operation",

docs/source/spec/aws-core.rst

@@ -39,7 +39,7 @@ The following example defines an AWS service that uses the default values of
 
     .. code-tab:: smithy
 
-        $version: "0.5.0"
+        $version: "1.0"
         namespace aws.fooBaz
 
         use aws.api#service
@@ -52,7 +52,7 @@ The following example defines an AWS service that uses the default values of
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "aws.fooBaz#FooBaz": {
                     "type": "service",
@@ -72,7 +72,7 @@ The following example provides explicit values for all properties:
 
     .. code-tab:: smithy
 
-        $version: "0.5.0"
+        $version: "1.0"
         namespace aws.fooBaz
 
         use aws.api#service
@@ -89,7 +89,7 @@ The following example provides explicit values for all properties:
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "aws.fooBaz#FooBaz": {
                     "type": "service",
@@ -386,7 +386,7 @@ For example, given the following service:
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#FooBaz": {
                     "type": "service",
@@ -452,7 +452,7 @@ resource.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyResource": {
                     "type": "resource",
@@ -551,7 +551,7 @@ referenced resource.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#SomeResourceId": {
                     "type": "string",
@@ -574,7 +574,7 @@ previous example:
 
     .. code-tab:: smithy
 
-        $version: "0.5.0"
+        $version: "1.0"
         namespace smithy.example
 
         use aws.api#arnReference
@@ -585,7 +585,7 @@ previous example:
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#SomeResourceId": {
                     "type": "string",
@@ -639,7 +639,7 @@ structure, union, or collection unless overridden.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyStructure": {
                     "type": "structure",
@@ -760,7 +760,7 @@ plane unless an operation or resource is marked with the
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#PutThings": {
                     "type": "operation",
@@ -814,7 +814,7 @@ plane unless an operation or resource is marked with the
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#PutThings": {
                     "type": "operation",
@@ -1010,7 +1010,7 @@ using an ``clientEndpointDiscoveryId``.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "ns.foo#FooService": {
                     "type": "service",

docs/source/spec/aws-iam.rst

@@ -51,7 +51,7 @@ Value type
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#FooOperation": {
                     "type": "operation",
@@ -112,7 +112,7 @@ The following example's ``MyResource`` resource has the
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",
@@ -235,7 +235,7 @@ Each condition key structure supports the following members:
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",
@@ -358,7 +358,7 @@ condition key inference disabled.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",
@@ -439,7 +439,7 @@ operation for it to complete successfully.
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",
@@ -535,7 +535,7 @@ Given the following model,
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",

docs/source/spec/aws-json-protocols.rst

@@ -45,7 +45,7 @@ See
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",
@@ -90,7 +90,7 @@ Value type
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",

docs/source/spec/aws-query-protocol.rst

@@ -44,7 +44,7 @@ See
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",
@@ -90,7 +90,7 @@ Value type
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",
@@ -133,7 +133,7 @@ when serializing an INPUT. For example, given the following Smithy model:
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyStruct": {
                     "type": "structure",

docs/source/spec/aws-restjson1-protocol.rst

@@ -44,7 +44,7 @@ See
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",

docs/source/spec/aws-restxml-protocol.rst

@@ -44,7 +44,7 @@ See
     .. code-tab:: json
 
         {
-            "smithy": "0.5.0",
+            "smithy": "1.0",
             "shapes": {
                 "smithy.example#MyService": {
                     "type": "service",