Skip to content

Commit 61e4dba

Browse files
committed
fix(ci): chain publish into release-please workflow
GITHUB_TOKEN releases don't trigger other workflows due to GitHub's recursive-trigger protection. Move publish/release jobs into the release-please caller workflow using the release_created output, so they run in the same workflow execution. Standalone trigger workflows changed to workflow_dispatch for manual use.
1 parent 270d6f6 commit 61e4dba

2 files changed

Lines changed: 8 additions & 3 deletions

File tree

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,10 @@
11
name: Publish to crates.io
22

33
on:
4-
release:
5-
types: [published]
4+
workflow_dispatch:
65

76
jobs:
87
publish:
98
uses: oxidized-mc/ci/.github/workflows/cargo-publish.yml@main
109
secrets:
1110
CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
12-

.github/workflows/release-please.yml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,3 +10,10 @@ jobs:
1010
permissions:
1111
contents: write
1212
pull-requests: write
13+
14+
publish:
15+
needs: [release]
16+
if: ${{ needs.release.outputs.release_created == 'true' }}
17+
uses: oxidized-mc/ci/.github/workflows/cargo-publish.yml@main
18+
secrets:
19+
CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}

0 commit comments

Comments
 (0)