From 19f8bcbfd4a6b8bb31a0f75cf22b59de6af100e5 Mon Sep 17 00:00:00 2001 From: Joe Lust Date: Tue, 12 Apr 2022 15:55:27 -0400 Subject: [PATCH] Doc update - release process [skip ci] --- CONTRIBUTING.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 754abb2..3166ad0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -28,3 +28,5 @@ git push origin v1 Once the tag exists, you make a new release from it in the github UI. Repeat the tagging process (no release needed) for the major version (e.g. `v1`) and delete/replace this tag, allowing users to peg against the major version in workflows and automatically get updates. + +Finally manually make a formal GitHub release [here](https://github.com/mablhq/github-run-tests-action/releases) for this new version and push it to the GitHub Actions Marketplace.