Skip to content

Commit bf4aa8e

Browse files
G4brymclaude
andcommitted
fix: use pre-check output for GitHub release condition
The changesets action doesn't set `published=true` when running a custom npm publish command with no changesets present. Use our own pre-publish check instead — if the version wasn't on npm before the workflow ran and the publish step succeeded, create the release. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 1b4c9a1 commit bf4aa8e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

.github/workflows/release.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ jobs:
6464
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
6565

6666
- name: Create GitHub Release
67-
if: steps.changesets.outputs.published == 'true'
67+
if: steps.check.outputs.published == 'false'
6868
run: |
6969
VERSION=$(jq -r .version packages/worker/package.json)
7070
TAG="v${VERSION}"

0 commit comments

Comments
 (0)