Commit bf4aa8e
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
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
64 | 64 | | |
65 | 65 | | |
66 | 66 | | |
67 | | - | |
| 67 | + | |
68 | 68 | | |
69 | 69 | | |
70 | 70 | | |
| |||
0 commit comments