Notify Discord on Release workflow (clusterzx/paperless-ai)

The Notify Discord on Release workflow from clusterzx/paperless-ai, explained and optimized by Latchkey.

CI health: B - good

Point runs-on at Latchkey and get job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: clusterzx/paperless-ai.github/workflows/release-to-discord.ymlLicense MITView source

What it does

This is the Notify Discord on Release workflow from the clusterzx/paperless-ai repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)

name: Notify Discord on Release

on:
  release:
    types: [published]

jobs:
  discord_notification:
    runs-on: ubuntu-latest
    steps:
      - name: Send Discord Notification
        uses: sarisia/actions-status-discord@v1.15.3
        with:
          webhook: ${{ secrets.DISCORD_WEBHOOK_URL }}
          username: "GitHub Bot 🤖"
          avatar_url: "https://github.githubassets.com/images/modules/logos_page/GitHub-Mark.png"
          content: |
            **🚀 New Release Published!**
            📌 **Repository:** `${{ github.repository }}`
            🏷️ **Version:** `${{ github.event.release.tag_name }}`
            📜 **Description:**
            ```
            ${{ github.event.release.body }}
            ```
            🔗 **[View Release](${{ github.event.release.html_url }})**
          embeds: |
            [
              {
                "title": "🎉 New Release: ${{ github.event.release.tag_name }}",
                "description": "${{ github.event.release.body }}",
                "url": "${{ github.event.release.html_url }}",
                "color": 16776960,
                "footer": {
                  "text": "GitHub Actions",
                  "icon_url": "https://github.githubassets.com/images/modules/logos_page/GitHub-Mark.png"
                },
                "timestamp": "${{ github.event.release.published_at }}"
              }
            ]

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Notify Discord on Release
 
on:
  release:
    types: [published]
 
jobs:
  discord_notification:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Send Discord Notification
        uses: sarisia/actions-status-discord@v1.15.3
        with:
          webhook: ${{ secrets.DISCORD_WEBHOOK_URL }}
          username: "GitHub Bot 🤖"
          avatar_url: "https://github.githubassets.com/images/modules/logos_page/GitHub-Mark.png"
          content: |
            **🚀 New Release Published!**
            📌 **Repository:** `${{ github.repository }}`
            🏷️ **Version:** `${{ github.event.release.tag_name }}`
            📜 **Description:**
            ```
            ${{ github.event.release.body }}
            ```
            🔗 **[View Release](${{ github.event.release.html_url }})**
          embeds: |
            [
              {
                "title": "🎉 New Release: ${{ github.event.release.tag_name }}",
                "description": "${{ github.event.release.body }}",
                "url": "${{ github.event.release.html_url }}",
                "color": 16776960,
                "footer": {
                  "text": "GitHub Actions",
                  "icon_url": "https://github.githubassets.com/images/modules/logos_page/GitHub-Mark.png"
                },
                "timestamp": "${{ github.event.release.published_at }}"
              }
            ]

What changed

Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
Add a job timeout so a hung step cannot burn hours of runner time.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.