@@ -376,35 +376,5 @@ jobs:
376376 --repo "$GITHUB_REPOSITORY" --target "$GITHUB_SHA" \
377377 --title "$TITLE" --notes "$NOTES" --latest
378378 fi
379-
380- # Propagate the engine to the lobby. A deploy key is git/SSH-only (it cannot
381- # call the API for repository_dispatch), so instead we push the new engine tag
382- # into a tracked file in ExaDev/bar-lobby. bar-lobby's release.yml triggers on
383- # push to macos-port and reads that file, so this both pins the lobby to an
384- # explicit engine version (reproducible — no "latest" race) and kicks a lobby
385- # rebuild. A deploy-key push (unlike a GITHUB_TOKEN push) does spawn the
386- # downstream workflow run.
387- bump-lobby :
388- name : Pin engine in bar-lobby
389- needs : build-macos-gpu
390- if : github.event_name == 'push' && needs.build-macos-gpu.outputs.engine_tag != ''
391- runs-on : ubuntu-latest
392- steps :
393- - name : Checkout bar-lobby via SSH deploy key
394- uses : actions/checkout@v6
395- with :
396- repository : ExaDev/bar-lobby
397- ref : macos-port
398- ssh-key : ${{ secrets.LOBBY_DEPLOY_KEY }}
399- - name : Write pinned engine tag and push
400- env :
401- ENGINE_TAG : ${{ needs.build-macos-gpu.outputs.engine_tag }}
402- run : |
403- set -euo pipefail
404- mkdir -p buildResources
405- printf '%s\n' "$ENGINE_TAG" > buildResources/engine-release.txt
406- git config user.name "github-actions[bot]"
407- git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
408- git add buildResources/engine-release.txt
409- git diff --cached --quiet || git commit -m "chore: pin engine ${ENGINE_TAG}"
410- git push
379+ # bar-lobby and the Chobby launcher now fetch this engine release
380+ # directly at runtime (no pin file), so there is no downstream bump job.
0 commit comments