Skip to content

Commit c57575e

Browse files
fix: Release workflow, which fails publish step & auto update readme by release-please-config (#551)
1 parent edee320 commit c57575e

File tree

2 files changed

+12
-11
lines changed

2 files changed

+12
-11
lines changed

.github/workflows/release-please.yml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -13,26 +13,26 @@ name: Release Please
1313
jobs:
1414
release-please:
1515
runs-on: ubuntu-latest
16+
outputs:
17+
release_created: ${{ steps.release.outputs.release_created }}
1618
steps:
1719
- uses: googleapis/release-please-action@v4
1820
id: release
1921
with:
2022
config-file: release-please-config.json
2123
manifest-file: .release-please-manifest.json
2224
token: ${{ secrets.SYNCED_GITHUB_TOKEN_REPO }}
23-
default-branch: main
25+
target-branch: main
2426

2527
- name: Echo release outputs
2628
if: ${{ steps.release.outputs }}
2729
run: echo '${{ toJson(steps.release) }}'
2830
continue-on-error: true
2931

30-
- name: Checkout
31-
uses: actions/checkout@v4
32-
33-
# Call the Publish workflow to publish to CocoaPods when a release is cut.
34-
# Note the "if" statement makes sure that publishing
35-
# only happens when a release is cut.
36-
- if: ${{ steps.release.outputs.release_created }}
37-
name: Start publish
38-
uses: ./.github/workflows/publish.yml
32+
# Call the Publish workflow to publish to CocoaPods when a release is cut.
33+
# Note the "if" statement makes sure that publishing
34+
# only happens when a release is cut.
35+
publish:
36+
needs: release-please
37+
if: ${{ needs.release-please.outputs.release_created }}
38+
uses: ./.github/workflows/publish.yml

release-please-config.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,8 @@
1010
"changelog-path": "CHANGELOG.md",
1111
"extra-files": [
1212
"Google-Maps-iOS-Utils.podspec",
13-
"Podfile.template"
13+
"Podfile.template",
14+
"README.md"
1415
]
1516
}
1617
}

0 commit comments

Comments
 (0)