Update checkout v2 to v3 in CI manifests

This commit is contained in:
Clémentine Urquizar 2022-09-02 16:45:32 +02:00
parent f45ddff312
commit 2eca723a91
No known key found for this signature in database
GPG Key ID: D8E7CC7422E77E1A
3 changed files with 3 additions and 3 deletions

View File

@ -12,7 +12,7 @@ jobs:
runs-on: ubuntu-latest runs-on: ubuntu-latest
# No need to check the version for dry run (cron) # No need to check the version for dry run (cron)
steps: steps:
- uses: actions/checkout@v2 - uses: actions/checkout@v3
# Check if the tag has the v<nmumber>.<number>.<number> format. # Check if the tag has the v<nmumber>.<number>.<number> format.
# If yes, it means we are publishing an official release. # If yes, it means we are publishing an official release.
# If no, we are releasing a RC, so no need to check the version. # If no, we are releasing a RC, so no need to check the version.

View File

@ -9,7 +9,7 @@ jobs:
name: Check the version validity name: Check the version validity
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- uses: actions/checkout@v2 - uses: actions/checkout@v3
- name: Check release validity - name: Check release validity
run: bash .github/scripts/check-release.sh run: bash .github/scripts/check-release.sh

View File

@ -12,7 +12,7 @@ jobs:
docker: docker:
runs-on: docker runs-on: docker
steps: steps:
- uses: actions/checkout@v2 - uses: actions/checkout@v3
# Check if the tag has the v<nmumber>.<number>.<number> format. If yes, it means we are publishing an official release. # Check if the tag has the v<nmumber>.<number>.<number> format. If yes, it means we are publishing an official release.
# In this situation, we need to set `output.stable` to create/update the following tags (additionally to the `vX.Y.Z` Docker tag): # In this situation, we need to set `output.stable` to create/update the following tags (additionally to the `vX.Y.Z` Docker tag):