Prepare all resources for release v0.4

Update all events, close -draft versions:
- ls examples | while read aa; do sp="$(echo ${aa%.*} | tr "_" ".")"; ./tools/event-version.sh -u $sp -e; done

Update the spec script to handle the custom events schema.
Update the spec:
- ./tools/spec-release.sh -e

Remove a couple of references to "-draft" versions from the
links.md document.

Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>

Author: afrittoli

continuous-deployment.md

@@ -51,7 +51,7 @@ A `service` can represent for example a binary that is running, a daemon, an app
 
 This event represents an environment that has been created. Such an environment can be used to deploy services in.
 
-- Event Type: __`dev.cdevents.environment.created.0.2.0-draft`__
+- Event Type: __`dev.cdevents.environment.created.0.2.0`__
 - Predicate: created
 - Subject: [`environment`](#environment)
 
@@ -67,7 +67,7 @@ This event represents an environment that has been created. Such an environment
 
 This event represents an environment that has been modified.
 
-- Event Type: __`dev.cdevents.environment.modified.0.2.0-draft`__
+- Event Type: __`dev.cdevents.environment.modified.0.2.0`__
 - Predicate: modified
 - Subject: [`environment`](#environment)
 
@@ -83,7 +83,7 @@ This event represents an environment that has been modified.
 
 This event represents an environment that has been deleted.```
 
-- Event Type: __`dev.cdevents.environment.deleted.0.2.0-draft`__
+- Event Type: __`dev.cdevents.environment.deleted.0.2.0`__
 - Predicate: deleted
 - Subject: [`environment`](#environment)
 
@@ -98,7 +98,7 @@ This event represents an environment that has been deleted.```
 
 This event represents a new instance of a service that has been deployed
 
-- Event Type: __`dev.cdevents.service.deployed.0.2.0-draft`__
+- Event Type: __`dev.cdevents.service.deployed.0.2.0`__
 - Predicate: deployed
 - Subject: [`service`](#service)
 
@@ -114,7 +114,7 @@ This event represents a new instance of a service that has been deployed
 
 This event represents an existing instance of a service that has been upgraded to a new version
 
-- Event Type: __`dev.cdevents.service.upgraded.0.2.0-draft`__
+- Event Type: __`dev.cdevents.service.upgraded.0.2.0`__
 - Predicate: upgraded
 - Subject: [`service`](#service)
 
@@ -130,7 +130,7 @@ This event represents an existing instance of a service that has been upgraded t
 
 This event represents an existing instance of a service that has been rolled back to a previous version
 
-- Event Type: __`dev.cdevents.service.rolledback.0.2.0-draft`__
+- Event Type: __`dev.cdevents.service.rolledback.0.2.0`__
 - Predicate: rolledback
 - Subject: [`service`](#service)
 
@@ -146,7 +146,7 @@ This event represents an existing instance of a service that has been rolled bac
 
 This event represents the removal of a previously deployed service instance and is thus not longer present in the specified environment
 
-- Event Type: __`dev.cdevents.service.removed.0.2.0-draft`__
+- Event Type: __`dev.cdevents.service.removed.0.2.0`__
 - Predicate: removed
 - Subject: [`service`](#service)
 
@@ -161,7 +161,7 @@ This event represents the removal of a previously deployed service instance and
 
 This event represents an existing instance of a service that has an accessible URL for users to interact with it. This event can be used to let other tools know that the service is ready and also available for consumption.
 
-- Event Type: __`dev.cdevents.service.published.0.2.0-draft`__
+- Event Type: __`dev.cdevents.service.published.0.2.0`__
 - Predicate: published
 - Subject: [`service`](#service)
 

continuous-integration.md

@@ -56,7 +56,7 @@ An `artifact` is usually produced as output of a build process. Events need to b
 
 This event represents a Build task that has been queued; this build process usually is in charge of producing a binary from source code.
 
-- Event Type: __`dev.cdevents.build.queued.0.2.0-draft`__
+- Event Type: __`dev.cdevents.build.queued.0.2.0`__
 - Predicate: queued
 - Subject: [`build`](#build)
 
@@ -70,7 +70,7 @@ This event represents a Build task that has been queued; this build process usua
 
 This event represents a Build task that has been started; this build process usually is in charge of producing a binary from source code.
 
-- Event Type: __`dev.cdevents.build.started.0.2.0-draft`__
+- Event Type: __`dev.cdevents.build.started.0.2.0`__
 - Predicate: started
 - Subject: [`build`](#build)
 
@@ -84,7 +84,7 @@ This event represents a Build task that has been started; this build process usu
 
 This event represents a Build task that has finished. This event will eventually contain the finished status, success, error or failure
 
-- Event Type: __`dev.cdevents.build.finished.0.2.0-draft`__
+- Event Type: __`dev.cdevents.build.finished.0.2.0`__
 - Predicate: finished
 - Subject: [`build`](#build)
 
@@ -100,7 +100,7 @@ This event represents a Build task that has finished. This event will eventually
 The event represents an artifact that has been packaged for distribution; this artifact is now versioned with a fixed version.
 This event is usually produced by the build system. If an SBOM URI is available at this stage, it should be included.
 
-- Event Type: __`dev.cdevents.artifact.packaged.0.2.0-draft`__
+- Event Type: __`dev.cdevents.artifact.packaged.0.2.0`__
 - Predicate: packaged
 - Subject: [`artifact`](#artifact)
 
@@ -117,7 +117,7 @@ This event is usually produced by the build system. If an SBOM URI is available
 The event represents an artifact that has been signed. The signature is included in the events itself.
 An artifact may be signed after it has been packaged or sometimes after it has published, depending on the tooling being used and the type of artifact. The `artifact signed` event is typically produced by the CI or build system.
 
-- Event Type: __`dev.cdevents.artifact.signed.0.2.0-draft`__
+- Event Type: __`dev.cdevents.artifact.signed.0.2.0`__
 - Predicate: signed
 - Subject: [`artifact`](#artifact)
 
@@ -133,7 +133,7 @@ An artifact may be signed after it has been packaged or sometimes after it has p
 The event represents an artifact that has been published and it can be advertised for others to use.
 The `artifact published` event is typically produced by the artifact registry, but it may also be produced by the build system.
 
-- Event Type: __`dev.cdevents.artifact.published.0.2.0-draft`__
+- Event Type: __`dev.cdevents.artifact.published.0.2.0`__
 - Predicate: published
 - Subject: [`artifact`](#artifact)
 
@@ -149,7 +149,7 @@ The `artifact published` event is typically produced by the artifact registry, b
 The event represents an artifact that has been downloaded from the registry.
 The `artifact downloaded` event is preferably produced by the artifact registry.
 
-- Event Type: __`dev.cdevents.artifact.downloaded.0.1.0-draft`__
+- Event Type: __`dev.cdevents.artifact.downloaded.0.1.0`__
 - Predicate: downloaded
 - Subject: [`artifact`](#artifact)
 
@@ -165,7 +165,7 @@ The `artifact downloaded` event is preferably produced by the artifact registry.
 The event represents an artifact that has been deleted from an artifact registry.
 The `artifact deleted` event is preferably produced by the artifact registry.
 
-- Event Type: __`dev.cdevents.artifact.deleted.0.1.0-draft`__
+- Event Type: __`dev.cdevents.artifact.deleted.0.1.0`__
 - Predicate: deleted
 - Subject: [`artifact`](#artifact)
 

continuous-operations.md

@@ -62,7 +62,7 @@ A ticket can request a change, report a problem, or document an [`incident`](#in
 
 This event represents an incident that has been detected by a system or human.
 
-- Event Type: __`dev.cdevents.incident.detected.0.2.0-draft`__
+- Event Type: __`dev.cdevents.incident.detected.0.2.0`__
 - Predicate: detected
 - Subject: [`incident`](#incident)
 
@@ -80,7 +80,7 @@ This event represents an incident that has been detected by a system or human.
 
 This event represents an incident that has been reported through a ticketing system. Compared to the `detected` predicated, it introduces a ticket URI.
 
-- Event Type: __`dev.cdevents.incident.reported.0.2.0-draft`__
+- Event Type: __`dev.cdevents.incident.reported.0.2.0`__
 - Predicate: reported
 - Subject: [`incident`](#incident)
 
@@ -99,7 +99,7 @@ This event represents an incident that has been reported through a ticketing sys
 
 This event represents an incident that has been resolved, meaning that the problem identified by the incident has been solved or recalled.
 
-- Event Type: __`dev.cdevents.incident.resolved.0.2.0-draft`__
+- Event Type: __`dev.cdevents.incident.resolved.0.2.0`__
 - Predicate: resolved
 - Subject: [`incident`](#incident)
 
@@ -117,7 +117,7 @@ This event represents an incident that has been resolved, meaning that the probl
 
 This event represents a ticket that has been created within some ticketing system.
 
-- Event Type: __`dev.cdevents.ticket.created.0.1.0-draft`__
+- Event Type: __`dev.cdevents.ticket.created.0.1.0`__
 - Predicate: created
 - Subject: [`ticket`](#ticket)
 
@@ -140,7 +140,7 @@ This event represents a ticket that has been created within some ticketing syste
 
 This event indicates that a ticket has been updated within some ticketing system.
 
-- Event Type: __`dev.cdevents.ticket.updated.0.1.0-draft`__
+- Event Type: __`dev.cdevents.ticket.updated.0.1.0`__
 - Predicate: updated
 - Subject: [`ticket`](#ticket)
 
@@ -164,7 +164,7 @@ This event indicates that a ticket has been updated within some ticketing system
 
 This event indicates that a ticket has been closed or resolved within some ticketing system.
 
-- Event Type: __`dev.cdevents.ticket.closed.0.1.0-draft`__
+- Event Type: __`dev.cdevents.ticket.closed.0.1.0`__
 - Predicate: closed
 - Subject: [`ticket`](#ticket)
 

core.md

@@ -68,7 +68,7 @@ Due the dynamic nature of Pipelines, most of actual work needs to be queued to
 happen in a distributed way, hence queued events are added. Adopters can choose
 to ignore these events if they don't apply to their use cases.
 
-- Event Type: __`dev.cdevents.pipelinerun.queued.0.2.0-draft`__
+- Event Type: __`dev.cdevents.pipelinerun.queued.0.2.0`__
 - Predicate: queued
 - Subject: [`pipelineRun`](#pipelinerun)
 
@@ -84,7 +84,7 @@ to ignore these events if they don't apply to their use cases.
 
 A pipelineRun has started and it is running.
 
-- Event Type: __`dev.cdevents.pipelinerun.started.0.2.0-draft`__
+- Event Type: __`dev.cdevents.pipelinerun.started.0.2.0`__
 - Predicate: started
 - Subject: [`pipelineRun`](#pipelinerun)
 
@@ -100,7 +100,7 @@ A pipelineRun has started and it is running.
 
 A pipelineRun has finished, successfully or not.
 
-- Event Type: __`dev.cdevents.pipelinerun.finished.0.2.0-draft`__
+- Event Type: __`dev.cdevents.pipelinerun.finished.0.2.0`__
 - Predicate: finished
 - Subject: [`pipelineRun`](#pipelinerun)
 
@@ -118,7 +118,7 @@ A pipelineRun has finished, successfully or not.
 
 A taskRun has started and it is running.
 
-- Event Type: __`dev.cdevents.taskrun.started.0.2.0-draft`__
+- Event Type: __`dev.cdevents.taskrun.started.0.2.0`__
 - Predicate: started
 - Subject: [`taskRun`](#taskrun)
 
@@ -135,7 +135,7 @@ A taskRun has started and it is running.
 
 A taskRun has finished, successfully or not.
 
-- Event Type: __`dev.cdevents.taskrun.finished.0.2.0-draft`__
+- Event Type: __`dev.cdevents.taskrun.finished.0.2.0`__
 - Predicate: finished
 - Subject: [`taskRun`](#taskrun)
 

custom/schema.json

@@ -1,6 +1,6 @@
 {
     "$schema": "https://json-schema.org/draft/2020-12/schema",
-    "$id": "https://cdevents.dev/0.4.0-draft/schema/custom",
+    "$id": "https://cdevents.dev/0.4.0/schema/custom",
     "properties": {
       "context": {
         "properties": {

examples/artifact_deleted.json

@@ -1,9 +1,9 @@
 {
   "context": {
-    "version": "0.4.0-draft",
+    "version": "0.4.0",
     "id": "271069a8-fc18-44f1-b38f-9d70a1695819",
     "source": "/event/source/123",
-    "type": "dev.cdevents.artifact.deleted.0.1.0-draft",
+    "type": "dev.cdevents.artifact.deleted.0.1.0",
     "timestamp": "2023-03-20T14:27:05.315384Z",
     "schemaUri": "https://myorg.com/schema/custom"
   },

examples/artifact_downloaded.json

@@ -1,9 +1,9 @@
 {
   "context": {
-    "version": "0.4.0-draft",
+    "version": "0.4.0",
     "id": "271069a8-fc18-44f1-b38f-9d70a1695819",
     "source": "/event/source/123",
-    "type": "dev.cdevents.artifact.downloaded.0.1.0-draft",
+    "type": "dev.cdevents.artifact.downloaded.0.1.0",
     "timestamp": "2023-03-20T14:27:05.315384Z",
     "schemaUri": "https://myorg.com/schema/custom"
   },

examples/artifact_packaged.json

@@ -1,10 +1,10 @@
 {
   "context": {
-    "version": "0.4.0-draft",
+    "version": "0.4.0",
     "id": "271069a8-fc18-44f1-b38f-9d70a1695819",
     "chain_id": "4c8cb7dd-3448-41de-8768-eec704e2829b",
     "source": "/event/source/123",
-    "type": "dev.cdevents.artifact.packaged.0.2.0-draft",
+    "type": "dev.cdevents.artifact.packaged.0.2.0",
     "timestamp": "2023-03-20T14:27:05.315384Z",
     "schemaUri": "https://myorg.com/schema/custom"
   },

examples/artifact_published.json

@@ -1,10 +1,10 @@
 {
   "context": {
-    "version": "0.4.0-draft",
+    "version": "0.4.0",
     "id": "271069a8-fc18-44f1-b38f-9d70a1695819",
     "chain_id": "4c8cb7dd-3448-41de-8768-eec704e2829b",
     "source": "/event/source/123",
-    "type": "dev.cdevents.artifact.published.0.2.0-draft",
+    "type": "dev.cdevents.artifact.published.0.2.0",
     "timestamp": "2023-03-20T14:27:05.315384Z",
     "schemaUri": "https://myorg.com/schema/custom"
   },

examples/artifact_signed.json

@@ -1,10 +1,10 @@
 {
   "context": {
-    "version": "0.4.0-draft",
+    "version": "0.4.0",
     "id": "271069a8-fc18-44f1-b38f-9d70a1695819",
     "chain_id": "4c8cb7dd-3448-41de-8768-eec704e2829b",
     "source": "/event/source/123",
-    "type": "dev.cdevents.artifact.signed.0.2.0-draft",
+    "type": "dev.cdevents.artifact.signed.0.2.0",
     "timestamp": "2023-03-20T14:27:05.315384Z",
     "schemaUri": "https://myorg.com/schema/custom"
   },