From 36a4b7df618f9172b8072b2706b4a4d7793d1baf Mon Sep 17 00:00:00 2001 From: Brian Cristante <33549821+brcrista@users.noreply.github.com> Date: Tue, 7 Apr 2020 09:42:56 -0400 Subject: [PATCH] Add screenshot to release instructions (#406) --- docs/action-versioning.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/action-versioning.md b/docs/action-versioning.md index 7b71f93c..4a8e8168 100644 --- a/docs/action-versioning.md +++ b/docs/action-versioning.md @@ -34,7 +34,9 @@ Binding to the immutable full sha1 may offer more reliability. However, note th 1. **Create a GitHub release for each specific version**: Creating a release like [ v1.0.0 ](https://github.com/actions/javascript-action/releases/tag/v1.0.0) allows users to bind back to a specific version if an issue is encountered with the latest major version. -2. **Publish the specific version to the marketplace**: When you release a specific version, choose the option to "Publish this release to the GitHub Marketplace". +2. **Publish the specific version to the marketplace**: When you release a specific version, choose the option to "Publish this Action to the GitHub Marketplace". + +screenshot 3. **Make the new release available to those binding to the major version tag**: Move the major version tag (v1, v2, etc.) to point to the ref of the current release. This will act as the stable release for that major version. You should keep this tag updated to the most recent stable minor/patch release.