From 2bf5fd112f5d71db1f2fbf2fa71d281ea981ddbf Mon Sep 17 00:00:00 2001 From: Sascha Mann Date: Mon, 16 Nov 2020 23:24:14 +0100 Subject: [PATCH] Fix version/sha examples in README --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 8fa80d5..50d7ffa 100644 --- a/README.md +++ b/README.md @@ -141,11 +141,11 @@ You can specify commits, branches or tags in your workflows as follows: ```yaml steps: - - uses: julia-actions/setup-julia@d26d1111976eae5f00db04f0515ab744ec9cd79e # commit SHA of the tagged 1.3.1 commit - - uses: julia-actions/setup-julia@master # branch + - uses: julia-actions/setup-julia@d3ce119a16594ea9e5d7974813970c73b6ab9e94 # commit SHA of the tagged 1.4.1 commit - uses: julia-actions/setup-julia@latest # latest version tag (may break existing workflows) - uses: julia-actions/setup-julia@v1 # major version tag - - uses: julia-actions/setup-julia@v0.1.0 # specific version tag + - uses: julia-actions/setup-julia@v1.4 # minor version tag + - uses: julia-actions/setup-julia@v1.4.1 # specific version tag ``` If your workflow requires access to secrets, you should always pin it to a commit SHA instead of a tag.