From 4c9436be96129ee93c5385b94c5e367691a2f675 Mon Sep 17 00:00:00 2001 From: Kevin Jones Date: Sun, 17 May 2026 19:57:12 +0100 Subject: [PATCH] ci: Fire publish workflows on prereleased events too The `release: types: [released]` trigger only matches when a GitHub release is published as non-prerelease. Creating a release with `--prerelease` (e.g. v2.0.0-beta.1) fires the separate `prereleased` event, so the publish workflows silently skipped and the artefacts had to be pushed via workflow_dispatch. Adding `prereleased` to the trigger list makes `gh release create --prerelease` publish to npm and Maven Central without a manual dispatch step. The npm dist-tag routing added in #18 already distinguishes pre-releases from stable versions, so this is safe. --- .github/workflows/PublishMaven.yml | 2 +- .github/workflows/PublishNPM.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/PublishMaven.yml b/.github/workflows/PublishMaven.yml index cc6ef01..6c7feb8 100644 --- a/.github/workflows/PublishMaven.yml +++ b/.github/workflows/PublishMaven.yml @@ -2,7 +2,7 @@ name: Publish to Maven on: release: - types: [ released ] + types: [ released, prereleased ] workflow_dispatch: jobs: diff --git a/.github/workflows/PublishNPM.yml b/.github/workflows/PublishNPM.yml index e1a23de..6f012a7 100644 --- a/.github/workflows/PublishNPM.yml +++ b/.github/workflows/PublishNPM.yml @@ -2,7 +2,7 @@ name: Publish to NPM on: release: - types: [ released ] + types: [ released, prereleased ] workflow_dispatch: jobs: