From 0324a92037f1c830fa1c9e440024211d423dbea5 Mon Sep 17 00:00:00 2001 From: Ivan Potiienko Date: Mon, 31 Aug 2026 22:28:13 +0200 Subject: Make release automation resilient to token expiry --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 81f3e15..a182761 100644 --- a/README.md +++ b/README.md @@ -105,7 +105,9 @@ Tagged releases build the platform binaries first, then trigger the Scoop bucket After all DEB and RPM assets have uploaded, the package workflow triggers the APT/RPM repository with the exact tag. The `RELEASE_TOKEN` Actions secret must be able to create repository dispatch events in `xxanqw/scoop-bucket`, `xxanqw/homebrew-mikusays`, and -`xxanqw/apt-repository`. +`xxanqw/apt-repository`. If that token expires, the release remains successful and the +downstream repositories recover through their scheduled update workflows. Uploads to the +MikuSays release itself use the built-in workflow token and do not depend on this secret. The distribution repositories keep scheduled and manual workflows as recovery paths if an event dispatch fails. -- cgit v1.3-2-g0d8e