From 31a2c9676bcb58af366066342e764bbb9be4b599 Mon Sep 17 00:00:00 2001 From: Layne Penney Date: Sun, 30 Aug 2026 07:44:35 -0500 Subject: [PATCH] ci(release): publish on tag push, not only on GitHub Release MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a 'push: tags: [v*]' trigger to both publish workflows so a tag push publishes to PyPI and npm, in addition to the existing 'release: published' path. Additive and idempotent — a 'gh release create ' that fires both events is safe: PyPI skip-existing and the npm already-published check no-op the second attempt. Deliberately NOT adding a tag<->package-version guard: this repo's version-sync-deferred design allows the PyPI and npm versions to diverge, so a strict tag==version assertion would fight that design. Flagged for synapt-side review (see PR body). Co-Authored-By: Claude Opus 4.8 --- .github/workflows/publish-npm.yml | 3 +++ .github/workflows/publish-pypi.yml | 3 +++ 2 files changed, 6 insertions(+) diff --git a/.github/workflows/publish-npm.yml b/.github/workflows/publish-npm.yml index d28bdf4..1f0af7d 100644 --- a/.github/workflows/publish-npm.yml +++ b/.github/workflows/publish-npm.yml @@ -1,6 +1,9 @@ name: Publish @synapt-dev/eval to npm on: + push: + tags: + - "v*" release: types: [published] workflow_dispatch: diff --git a/.github/workflows/publish-pypi.yml b/.github/workflows/publish-pypi.yml index 04d1397..f284d68 100644 --- a/.github/workflows/publish-pypi.yml +++ b/.github/workflows/publish-pypi.yml @@ -1,6 +1,9 @@ name: Publish synapt-eval to PyPI on: + push: + tags: + - "v*" release: types: [published]