diff --git a/action.yml b/action.yml
index 072d544..022f865 100644
--- a/action.yml
+++ b/action.yml
@@ -57,6 +57,8 @@ outputs:
     description: "The version tag"
   changed:
     description: "Indicates whether there was a change since the last version if change_path was specified. If no change_path was specified this value will always be true since the entire repo is considered."
+  authors:
+    description: "List of users contributing commits to this version"
 runs:
   using: "node16"
   main: "dist/index.js"
\ No newline at end of file
diff --git a/readme.md b/readme.md
index 463f30c..3e36992 100644
--- a/readme.md
+++ b/readme.md
@@ -92,6 +92,10 @@ it will be given the new version if the build were to be retriggered, for exampl
     short_tags: true
     # If this is set to true, *every* commit will be treated as a new version.
     bump_each_commit: false
+    # If true, the body of commits will also be searched for major/minor patterns to determine the version type.
+    search_commit_body: false
+    # The output method used to generate list of users, 'csv' or 'json'.
+    user_format_type: "csv"
 ```
 
 ## Outputs 
@@ -101,6 +105,7 @@ it will be given the new version if the build were to be retriggered, for exampl
 - *version* is a formatted version string created using the format input. This is a convenience value to provide a preformatted representation of the data generated by this action.
 - *version_tag* is a string identifier that would be used to tag the current commit as the "released" version. Typically this would only be used to generate a Git tag name.
 - *changed* indicates whether there was a change since the last version if change_path was specified. If no `change_path` was specified this value will always be true since the entire repo is considered. (It is possible to create a commit with no changes, but the Git cli rejects this by default and this case is not considered here)
+- *authors* is a list of authors that have committed to this version, formatted as either csv or json.
 
 There are two types of "version" string, one is the semantic version output that can be used to identify a build and can include prerelease data and metadata specific to the commit such as `v2.0.1-pre001+cf6e75` (you would produce this string yourself using the version information from this action plus whatever metadata you wanted to add), the other is the tag version string, which identifies a specific commit as being a specific version.