From afe8770b9951c13632bb346db937ec2cb0f8e2af Mon Sep 17 00:00:00 2001 From: Amadeusz Sadowski Date: Wed, 8 Mar 2023 23:50:20 +0100 Subject: [PATCH] deps: use latest versions of Github Actions --- .github/RELEASE_TEMPLATE.md | 33 ------------- .github/workflows/ReleaseIssue.yml | 72 ++++++++++++++++++++-------- .github/workflows/chatops.yml | 4 +- .github/workflows/ci.yml | 4 +- .github/workflows/publish-catpkg.yml | 2 +- 5 files changed, 56 insertions(+), 59 deletions(-) delete mode 100644 .github/RELEASE_TEMPLATE.md diff --git a/.github/RELEASE_TEMPLATE.md b/.github/RELEASE_TEMPLATE.md deleted file mode 100644 index 882f7b316d..0000000000 --- a/.github/RELEASE_TEMPLATE.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -labels: "Type: Release Thread" ---- -Data Developers - Please use this issue to push new releases if doing so via comment. - -# Explainer - -- Create an issue comment that starts with `/release` on the first line. -- Second (non-empty) line will be used as a release title/name. -- All following lines will be interpreted as a release description/body. -- Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release. - -# How to - -Add a comment with one of the following to push a release: - -### For a standard release: -*given latest release v2.2.2, will create a release v2.2.3 (increases patch)* -> /release -> -> This is title of v2.2.3 - -### For a Chapter Approved/Big FAQ initial releases (game-wide updates): -*given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)* -> /release bump=minor -> -> This is title of v2.3.0 - -### For a new game edition: -*given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)* -> /release bump=major -> -> This is title of v3.0.0 diff --git a/.github/workflows/ReleaseIssue.yml b/.github/workflows/ReleaseIssue.yml index 010af74d89..020721da22 100644 --- a/.github/workflows/ReleaseIssue.yml +++ b/.github/workflows/ReleaseIssue.yml @@ -3,30 +3,60 @@ name: Monthly Release Thread on: schedule: - - cron: 0 0 1 * * # Every 1st day of the month at 0000 – https://crontab.guru + - cron: 0 0 1 * * # Every 1st day of the month at 0000 – https://crontab.guru jobs: monthly_release: runs-on: ubuntu-latest steps: + # Get current month for issue title + - name: get-date + id: date + run: echo "date=$(date +'%B %Y')" >> $GITHUB_OUTPUT -# Repo code checkout required if `template` is used - - name: Checkout - uses: actions/checkout@v2 - -# Get current month for issue title - - name: get-date - id: date - run: echo "::set-output name=date::$(date +'%B %Y')" - -# Create, pin, label, and assign release issue - - name: create-issue - id: issue - uses: imjohnbo/issue-bot@v2 - with: - pinned: true - close-previous: true - title: "RELEASE THREAD: ${{ steps.date.outputs.date }}" - template: ".github/RELEASE_TEMPLATE.md" - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + # Create, pin, label, and assign release issue + - name: create-issue + id: issue + uses: imjohnbo/issue-bot@v3 + with: + pinned: true + close-previous: true + labels: "Type: Release Thread" + title: "RELEASE THREAD: ${{ steps.date.outputs.date }}" + body: | + Data Developers - Please use this issue to push new releases if doing so via comment. + + # Explainer + + - Create an issue comment that starts with `/release` on the first line. + - Second (non-empty) line will be used as a release title/name. + - All following lines will be interpreted as a release description/body. + - Description (even if empty) will always be appended with a comparison link to the previous release, unless there is no previous release. + + # How to + + Add a comment with one of the following to push a release: + + ### For a standard release: + + *given latest release v2.2.2, will create a release v2.2.3 (increases patch)* + > /release + > + > This is title of v2.2.3 + + ### For a Chapter Approved/Big FAQ initial releases (game-wide updates): + + *given latest release v2.2.2, will create a release v2.3.0 (increases minor, resets patch)* + > /release bump=minor + > + > This is title of v2.3.0 + + ### For a new game edition: + + *given latest release v2.2.2, will create a release v3.0.0 (increases major, resets minor and patch)* + > /release bump=major + > + > This is title of v3.0.0 + + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/chatops.yml b/.github/workflows/chatops.yml index f0812f6cea..46d9f6cdfd 100644 --- a/.github/workflows/chatops.yml +++ b/.github/workflows/chatops.yml @@ -9,12 +9,12 @@ jobs: if: startsWith(github.event.comment.body, '/') steps: - name: Checkout ChatOps repo - uses: actions/checkout@v2 + uses: actions/checkout@v3 with: repository: BSData/chatops path: chatops - name: /command dispatch - uses: peter-evans/slash-command-dispatch@v2 + uses: peter-evans/slash-command-dispatch@v3 with: token: ${{ secrets.SLASH_COMMAND_DISPATCH_TOKEN }} config-from-file: chatops/commands.json diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index c0e8e9d16b..54058275bb 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -7,12 +7,12 @@ jobs: build: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v3 - uses: BSData/check-datafiles@v1 id: check - - uses: actions/upload-artifact@v1 + - uses: actions/upload-artifact@v3 with: name: artifact path: ${{ steps.check.outputs.staging-path }} diff --git a/.github/workflows/publish-catpkg.yml b/.github/workflows/publish-catpkg.yml index 07cb419aa0..da1d260d04 100644 --- a/.github/workflows/publish-catpkg.yml +++ b/.github/workflows/publish-catpkg.yml @@ -8,5 +8,5 @@ jobs: publish: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v3 - uses: BSData/publish-catpkg@v1