Release workflow (7Sageer/sublink-worker)
The Release workflow from 7Sageer/sublink-worker, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Release workflow from the 7Sageer/sublink-worker 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
name: Release
on:
push:
tags:
- "v*.*.*" # Trigger on version tags like v2.0.1
permissions:
contents: write # Required to create releases
jobs:
release:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 0 # Fetch all history for changelog generation
- name: Extract version from tag
id: version
run: echo "VERSION=${GITHUB_REF#refs/tags/}" >> $GITHUB_OUTPUT
- name: Create GitHub Release
uses: softprops/action-gh-release@v1
with:
name: Sublink Worker ${{ steps.version.outputs.VERSION }}
body: |
## Release ${{ steps.version.outputs.VERSION }}
### π Documentation
- [Complete Changelog](https://sublink.works/updates/)
- [Deployment Guide](https://sublink.works/guide/quick-start/)
- [API Documentation](https://sublink.works/api/)
### π Quick Start
```bash
# Cloudflare Workers
npm install && npm run deploy
# Docker
docker compose up -d
# Node.js
npm run build:node && npm run dev:node
```
---
**Note:** This release was automatically created by GitHub Actions.
For detailed changes, see the [changelog](https://sublink.works/updates/).
generate_release_notes: true # Auto-generate notes from commits
draft: false
prerelease: false
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Notify success
if: success()
run: |
echo "β
Release ${{ steps.version.outputs.VERSION }} created successfully!"
echo "View at: ${{ github.server_url }}/${{ github.repository }}/releases/tag/${{ steps.version.outputs.VERSION }}"
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Release on: push: tags: - "v*.*.*" # Trigger on version tags like v2.0.1 permissions: contents: write # Required to create releases concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: release: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Checkout code uses: actions/checkout@v4 with: fetch-depth: 0 # Fetch all history for changelog generation - name: Extract version from tag id: version run: echo "VERSION=${GITHUB_REF#refs/tags/}" >> $GITHUB_OUTPUT - name: Create GitHub Release uses: softprops/action-gh-release@v1 with: name: Sublink Worker ${{ steps.version.outputs.VERSION }} body: | ## Release ${{ steps.version.outputs.VERSION }} ### π Documentation - [Complete Changelog](https://sublink.works/updates/) - [Deployment Guide](https://sublink.works/guide/quick-start/) - [API Documentation](https://sublink.works/api/) ### π Quick Start ```bash # Cloudflare Workers npm install && npm run deploy # Docker docker compose up -d # Node.js npm run build:node && npm run dev:node ``` --- **Note:** This release was automatically created by GitHub Actions. For detailed changes, see the [changelog](https://sublink.works/updates/). generate_release_notes: true # Auto-generate notes from commits draft: false prerelease: false env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - name: Notify success if: success() run: | echo "β Release ${{ steps.version.outputs.VERSION }} created successfully!" echo "View at: ${{ github.server_url }}/${{ github.repository }}/releases/tag/${{ steps.version.outputs.VERSION }}"
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 useslatchkey-small; pick the runner size that fits the job. - Cancel superseded runs when a branch or PR gets a newer push.
- 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.
What Latchkey heals here
This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:
- Dependency installs
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.