From 17240857e941c703e2c8f475a3f0fdf298a5ca15 Mon Sep 17 00:00:00 2001 From: Rousan Ali Date: Fri, 7 Aug 2026 05:51:52 +0530 Subject: [PATCH] Allow the release workflow to be run by hand 1.4.0 was merged to main during a GitHub Actions outage. No workflow ran for the merge, GitHub does not backfill missed runs, and with only a push trigger the only way to release was to push another commit to main purely to make something happen. workflow_dispatch is safe here for the same reason the push path is: the job skips when the tag for package.json's current version already exists, so running it by hand can rescue a missed release but can never double-publish one. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_018fw9DsmQqKxkhh9vbXmyqs --- .github/workflows/release.yml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 3412eeb..dd2acb6 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -6,6 +6,9 @@ # with auto-generated notes. Plain pushes that don't bump the version re-run this # but skip (the tag already exists), so no accidental re-release. # +# It can also be run by hand from the Actions tab, for when the push that should +# have released never got a run — see the note on the trigger below. +# # Requires a repository secret named NPM_TOKEN: an npm automation token with # publish rights to the @rousan scope. @@ -14,6 +17,14 @@ name: Release on: push: branches: [main] + # Manual trigger, because a push is not always available when you need one. + # 1.4.0 was merged to main during a GitHub Actions outage: no workflow ran for + # the merge, GitHub does not backfill missed runs, and with no dispatch trigger + # the only way to release was to push another commit to main purely to make + # something happen. Safe for the same reason the push path is — the job below + # skips when the tag for the current version already exists — so running this + # by hand can rescue a missed release but can never double-publish one. + workflow_dispatch: permissions: contents: write