You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: use BUMPY_GH_TOKEN for draft release operations
The draft release functions (createDraftRelease, updateReleaseBody,
finalizeRelease, deleteRelease) were not using withReleaseToken, so
GitHub release events were created with GITHUB_TOKEN which doesn't
trigger downstream workflows like on-release.yaml.
Copy file name to clipboardExpand all lines: .bumpy/disable-staged-publishing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
'@varlock/bumpy': patch
3
3
---
4
4
5
-
Disable npm staged publishing — feature is not yet ready for production use. Removes `npmStaged` config and the npm upgrade step from the release workflow.
5
+
Disable npm staged publishing — feature is not yet ready for production use. Removes `npmStaged` config and the npm upgrade step from the release workflow. Also fix draft release functions (`createDraftRelease`, `updateReleaseBody`, `finalizeRelease`, `deleteRelease`) to use `BUMPY_GH_TOKEN` via `withReleaseToken` so that GitHub release events trigger downstream workflows.
0 commit comments