release-please workflow (splx-ai/agentic-radar)
The release-please workflow from splx-ai/agentic-radar, explained and optimized by Latchkey.
CI health: F - at risk
Point runs-on at Latchkey and get caching, 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-please workflow from the splx-ai/agentic-radar repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
on:
push:
branches:
- main
name: release-please
permissions:
contents: write
pull-requests: write
id-token: write
env:
POETRY_VERSION: 2.0.1
jobs:
release-please:
runs-on: ubuntu-latest
steps:
- uses: googleapis/release-please-action@v4
id: release
with:
release-type: python
- uses: actions/checkout@v4
if: ${{ steps.release.outputs.release_created }}
- uses: actions/setup-python@v5
if: ${{ steps.release.outputs.release_created }}
with:
python-version: '3.11'
- name: Install poetry
if: ${{ steps.release.outputs.release_created }}
run: curl -sSL https://install.python-poetry.org | python3 - --version $POETRY_VERSION
- name: Install dependencies
if: ${{ steps.release.outputs.release_created }}
run: |
poetry install --all-extras
- name: Run tests
if: ${{ steps.release.outputs.release_created }}
run: |
poetry run python -m pytest -v -s
- name: Run checks
if: ${{ steps.release.outputs.release_created }}
run: |
poetry run ruff check
poetry run mypy agentic_radar
- name: Build
if: ${{ steps.release.outputs.release_created }}
run: poetry build
- name: Publish pypi
if: ${{ steps.release.outputs.release_created }}
uses: pypa/gh-action-pypi-publish@release/v1
The same workflow, on Latchkey
Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.
on: push: branches: - main name: release-please permissions: contents: write pull-requests: write id-token: write env: POETRY_VERSION: 2.0.1 concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: release-please: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: googleapis/release-please-action@v4 id: release with: release-type: python - uses: actions/checkout@v4 if: ${{ steps.release.outputs.release_created }} - uses: actions/setup-python@v5 if: ${{ steps.release.outputs.release_created }} with: cache: 'pip' python-version: '3.11' - name: Install poetry if: ${{ steps.release.outputs.release_created }} run: curl -sSL https://install.python-poetry.org | python3 - --version $POETRY_VERSION - name: Install dependencies if: ${{ steps.release.outputs.release_created }} run: | poetry install --all-extras - name: Run tests if: ${{ steps.release.outputs.release_created }} run: | poetry run python -m pytest -v -s - name: Run checks if: ${{ steps.release.outputs.release_created }} run: | poetry run ruff check poetry run mypy agentic_radar - name: Build if: ${{ steps.release.outputs.release_created }} run: poetry build - name: Publish pypi if: ${{ steps.release.outputs.release_created }} uses: pypa/gh-action-pypi-publish@release/v1
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.
- Cache dependency installs on the setup step so they are served from cache.
- Add a job timeout so a hung step cannot burn hours of runner time.
2 third-party actions are referenced by a movable tag. Pin them 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
- Network fetches
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.