From 1d2c43331cf22f5d1c30a6456d5b799228382e25 Mon Sep 17 00:00:00 2001
From: mleader <mleader@redhat.com>
Date: Tue, 17 Oct 2023 14:31:39 -0400
Subject: [PATCH 1/2] update readme

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f86fb4f5..2105644e 100644
--- a/README.md
+++ b/README.md
@@ -21,6 +21,7 @@ This binary can then be used to run Arcaflow workflows.
 The simplest workflow is the example plugin workflow: (save it to workflow.yaml)
 
 ```yaml
+version: v0.1.0
 input:
   root: RootObject
   objects:
@@ -89,7 +90,7 @@ deployment:
   host: # Host options, see https://docs.docker.com/engine/api/v1.41/#tag/Container/operation/ContainerCreate
   network: # Network options, see https://docs.docker.com/engine/api/v1.41/#tag/Container/operation/ContainerCreate
   platform: # Platform options, see https://docs.docker.com/engine/api/v1.41/#tag/Container/operation/ContainerCreate
-  
+
   # Pull policy, similar to Kubernetes
   imagePullPolicy: Always|IfNotPresent|Never
 timeouts:

From b65804cd12d60c43a6a7b299f4a0ab993dece591 Mon Sep 17 00:00:00 2001
From: mleader <mleader@redhat.com>
Date: Thu, 19 Oct 2023 12:03:53 -0400
Subject: [PATCH 2/2] clarify workflow schema version and supported versions

---
 README.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 2105644e..a5fd2b23 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ This binary can then be used to run Arcaflow workflows.
 
 ## Building a simple workflow
 
-The simplest workflow is the example plugin workflow: (save it to workflow.yaml)
+The simplest workflow is the example plugin workflow using the workflow schema version `v0.1.0`: (save it to workflow.yaml)
 
 ```yaml
 version: v0.1.0
@@ -44,7 +44,7 @@ output:
   message: !expr $.steps.example.outputs.success.message
 ```
 
-As you can see, it has an input, a list of steps, and an output definition. These can be linked together using JSONPath expressions (not all features are supported). The expressions also determine the execution order of plugins.
+As you can see, it has a `version`, `input`, a list of `steps`, and an `output` definition. Each of these keys is required in a workflow. These can be linked together using JSONPath expressions (not all features are supported). The expressions also determine the execution order of plugins.
 
 You can now create an input YAML for this workflow: (save it to input.yaml)
 
@@ -70,6 +70,10 @@ log:
 
 You can load this config by passing the `-config` flag to Arcaflow.
 
+### Supported Workflow Schema Versions
+
+- v0.1.0
+
 ## Deployer options
 
 Currently, the two deployer types supported are Docker and Kubernetes.