This repository was archived by the owner on Aug 21, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 21, 2026. It is now read-only.
Add repository_dispatch: [asobi-released] trigger to bump-asobi-pin.yml #130
Description
widgrensit/asobi#276 is fixed by widgrensit/asobi#315: asobi's release workflow now fires a repository_dispatch at this repo on every tagged release (event_type: asobi-released, client_payload.tag).
bump-asobi-pin.yml ignores it until it declares the trigger:
on:
schedule:
- cron: '30 4 * * *'
workflow_dispatch:
repository_dispatch:
types: [asobi-released]Until then the dispatch is accepted and dropped, and the nightly schedule stays the only path - the up-to-a-day lag from #103 remains.
The stale note in the workflow header ("Fastest fix (#103 option 1, not implemented here)") should go at the same time.
Also needs, on the asobi side: a repo secret ASOBI_LUA_DISPATCH_TOKEN scoped to dispatch into this repo.
Activity
Taure commentedon Aug 4, 2026
Obsolete on both halves. This asked to add
repository_dispatch: types: [asobi-released]to bump-asobi-pin.yml so asobi releases reached this repo faster.That workflow is deleted by #135 - it would have bumped the pin past the merge commit and made the image unbuildable, since asobi and asobi_lua defined the same 16 modules. And the repo it was speeding up no longer has source to update: the runtime lives in widgrensit/asobi, and this repo is now a packaging alias pinned to a release tag.
The asobi-side dispatcher (asobi's release.yml notify-asobi-lua job, scripts/dispatch-asobi-lua-pin-bump.sh) is inert - it fires a repository_dispatch event no workflow here declares, so GitHub accepts and drops it. Removing it is tracked separately.