Release v1.1.1

Signed-off-by: Brandon Mitchell <[email protected]>

Author: sudo-bmitch

README.md

@@ -20,7 +20,7 @@ Additional documentation about how this group operates:
 ## Running an OCI Image
 
 The OCI Image Format partner project is the [OCI Runtime Spec project](https://github.com/opencontainers/runtime-spec).
-The Runtime Specification outlines how to run a "[filesystem bundle](https://github.com/opencontainers/runtime-spec/blob/main/bundle.md)" that is unpacked on disk.
+The Runtime Specification outlines how to run a "[filesystem bundle](https://github.com/opencontainers/runtime-spec/blob/v1.2.0/bundle.md)" that is unpacked on disk.
 At a high-level an OCI implementation would download an OCI Image then unpack that image into an OCI Runtime filesystem bundle.
 At this point the OCI Runtime Bundle would be run by an OCI Runtime.
 

considerations.md

@@ -138,10 +138,10 @@ The above can be converted into the following regular expression:
 ```
 
 [canonical-json]: https://wiki.laptop.org/go/Canonical_JSON
-[distribution-spec]: https://github.com/opencontainers/distribution-spec/blob/main/spec.md
+[distribution-spec]: https://github.com/opencontainers/distribution-spec/blob/v1.1.1/spec.md
 [docker-go]: https://github.com/docker/go/
 [ebnf]: https://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_form
 [Go]: https://golang.org/
 [JSON]: https://json.org/
-[runtime-spec]: https://github.com/opencontainers/runtime-spec/blob/main/spec.md
+[runtime-spec]: https://github.com/opencontainers/runtime-spec/blob/v1.2.0/spec.md
 [xmlebnf]: https://www.w3.org/TR/REC-xml/#sec-notation

conversion.md

@@ -126,5 +126,5 @@ If there is a conflict (same key but different value) between an implicit annota
 A converter MAY add annotations which have keys not specified in the image.
 A converter MUST NOT modify the values of annotations specified in the image.
 
-[oci-runtime-bundle]: https://github.com/opencontainers/runtime-spec/blob/main/bundle.md
-[oci-runtime-config]: https://github.com/opencontainers/runtime-spec/blob/main/config.md
+[oci-runtime-bundle]: https://github.com/opencontainers/runtime-spec/blob/v1.2.0/bundle.md
+[oci-runtime-config]: https://github.com/opencontainers/runtime-spec/blob/v1.2.0/config.md

image-index.md

@@ -185,6 +185,6 @@ These values SHOULD match (or be similar to) their analog listed in [the Go Lang
 [go-environment2]: https://golang.org/doc/install/source#environment
 [iana]:            https://www.iana.org/assignments/media-types/media-types.xhtml
 [matrix]:          media-types.md#compatibility-matrix
-[referrers-api]:   https://github.com/opencontainers/distribution-spec/blob/main/spec.md#listing-referrers
+[referrers-api]:   https://github.com/opencontainers/distribution-spec/blob/v1.1.1/spec.md#listing-referrers
 [rfc6838]:         https://tools.ietf.org/html/rfc6838
 [rfc6838-s4.2]:    https://tools.ietf.org/html/rfc6838#section-4.2

image-layout.md

@@ -3,11 +3,11 @@
 - The OCI Image Layout is the directory structure for OCI content-addressable blobs and [location-addressable](https://en.wikipedia.org/wiki/Content-addressable_storage#Content-addressed_vs._location-addressed) references (refs).
 - This layout MAY be used in a variety of different transport mechanisms: archive formats (e.g. tar, zip), shared filesystem environments (e.g. nfs), or networked file fetching (e.g. http, ftp, rsync).
 
-Given an image layout and a ref, a tool can create an [OCI Runtime Specification bundle](https://github.com/opencontainers/runtime-spec/blob/main/bundle.md) by:
+Given an image layout and a ref, a tool can create an [OCI Runtime Specification bundle](https://github.com/opencontainers/runtime-spec/blob/v1.2.0/bundle.md) by:
 
 - Following the ref to find a [manifest](manifest.md#image-manifest), possibly via an [image index](image-index.md)
 - [Applying the filesystem layers](layer.md#applying) in the specified order
-- Converting the [image configuration](config.md) into an [OCI Runtime Specification `config.json`](https://github.com/opencontainers/runtime-spec/blob/main/config.md)
+- Converting the [image configuration](config.md) into an [OCI Runtime Specification `config.json`](https://github.com/opencontainers/runtime-spec/blob/v1.2.0/config.md)
 
 ## Content
 

manifest.md

@@ -265,6 +265,6 @@ _Implementers note:_ artifacts have historically been created without an `artifa
 
 [dag]:           https://en.wikipedia.org/wiki/Merkle_tree
 [iana]:          https://www.iana.org/assignments/media-types/media-types.xhtml
-[referrers-api]: https://github.com/opencontainers/distribution-spec/blob/main/spec.md#listing-referrers
+[referrers-api]: https://github.com/opencontainers/distribution-spec/blob/v1.1.1/spec.md#listing-referrers
 [rfc6838]:       https://tools.ietf.org/html/rfc6838
 [rfc6838-s4.2]:  https://tools.ietf.org/html/rfc6838#section-4.2

spec.md

@@ -42,7 +42,7 @@ Typically, these manifests may provide different implementations of the image, p
 
 ![build diagram](img/build-diagram.png)
 
-Once built the OCI Image can then be discovered by name, downloaded, verified by hash, trusted through a signature, and unpacked into an [OCI Runtime Bundle](https://github.com/opencontainers/runtime-spec/blob/main/bundle.md).
+Once built the OCI Image can then be discovered by name, downloaded, verified by hash, trusted through a signature, and unpacked into an [OCI Runtime Bundle](https://github.com/opencontainers/runtime-spec/blob/v1.2.0/bundle.md).
 
 ![runtime diagram](img/run-diagram.png)
 

specs-go/version.go

@@ -22,10 +22,10 @@ const (
 	// VersionMinor is for functionality in a backwards-compatible manner
 	VersionMinor = 1
 	// VersionPatch is for backwards-compatible bug fixes
-	VersionPatch = 0
+	VersionPatch = 1
 
 	// VersionDev indicates development branch. Releases will be empty string.
-	VersionDev = "+dev"
+	VersionDev = ""
 )
 
 // Version is the specification version that the package types support.