From cd1afbd7852b7ad7b1b7a9a1b03efebd3b0a1820 Mon Sep 17 00:00:00 2001 From: Harry Marr Date: Sat, 3 Feb 2024 11:07:23 -0500 Subject: [PATCH] Update version in README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 7f081f8..bf96121 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ Secrets are automatically filtered in the Actions logs. ## Usage instructions -Add a step with `- uses: hmarr/debug-action@v2` to a workflow file. Here's an example of a complete workflow file: +Add a step with `- uses: hmarr/debug-action@v3` to a workflow file. Here's an example of a complete workflow file: ```yaml name: Debug @@ -21,7 +21,7 @@ jobs: build: runs-on: ubuntu-latest steps: - - uses: hmarr/debug-action@v2 + - uses: hmarr/debug-action@v3 ``` @@ -78,5 +78,5 @@ That example is truncated a bit, but you get the idea. ## Development and release process Each major version corresponds to a branch (e.g. `v1`, `v2`). The latest major -version (`v2` at the time of writing) is the repository's default branch. +version (`v3` at the time of writing) is the repository's default branch. Releases are tagged with semver-style version numbers (e.g. `v1.2.3`).