Merge pull request #390 from vdice/chore/cnab-claims-1.0.0

chore(400-claims.md): update version in anticipation of the 1.0.0 release
cnabio · Oct 14, 2020 · 0dd834c · 0dd834c
2 parents fc40660 + 53f83f9
commit 0dd834c
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/400-claims.md b/400-claims.md
@@ -3,10 +3,10 @@ title: Claims System
 weight: 400
 ---
 
-# CNAB Claims 1.0 (CNAB-Claims1)
-Draft, Apr. 2020
+# CNAB Claims 1.0.0 (CNAB-Claims1)
+*[Final Approval, Published](901-process.md), Oct. 2020*
 
-This specification describes the CNAB Claims system. This is not part of the [CNAB Core](100-CNAB.md) specification, but is a specification describing how records of CNAB installations may be formatted for storage. Implementations of CNAB Core can meet the CNAB Core specification without implementing this specification. Implementations that support claims MAY state that they comply with CNAB Claims 1.0-WD.
+This specification describes the CNAB Claims system. This is not part of the [CNAB Core](100-CNAB.md) specification, but is a specification describing how records of CNAB installations may be formatted for storage. Implementations of CNAB Core can meet the CNAB Core specification without implementing this specification. Implementations that support claims MAY state that they comply with CNAB Claims 1.0.0.
 
 In CNAB, an _installation_ is a particular installed instance of a CNAB bundle. For example, if a bundle named `myApp` is installed in two places, we say there are _two installations of `myApp`_.
 
@@ -258,7 +258,7 @@ into the invocation container at runtime:
 - `$CNAB_BUNDLE_NAME`: The name of the present bundle.
 - `$CNAB_ACTION`: The action to be performed (install, upgrade, ...)
 - `$CNAB_REVISION`: The ULID for the present revision. (On upgrade, this is the _new_ revision)
-- `$CNAB_CLAIMS_VERSION`: The version of this specification (currently `CNAB-Claims-1.0-WD`)
+- `$CNAB_CLAIMS_VERSION`: The version of this specification (currently `CNAB-Claims-1.0.0`)
 
 > Credential data, which is also injected into the invocation image, is _not_ managed by the claim system. Rules for injecting credentials are found in [the bundle runtime definition](103-bundle-runtime.md).