mirror of
https://github.com/subsurface/subsurface.git
synced 2024-12-04 16:11:28 +00:00
30efede730
In order to make it easier to see what's happening inside get-atomic-buildnr.sh write the result to a file that can be read by the caller. Not quite as elegant, but hopefully more practical to see what's going wrong when no new build number is created. Make sure that post-releasenotes is successfull by actually posting a release artifact (apparently the gh release action otherwise quietly fails). Try to ensure we find the Android APK when uploading to the release. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
32 lines
958 B
YAML
32 lines
958 B
YAML
name: Post Release
|
|
on:
|
|
push:
|
|
branches:
|
|
- master
|
|
|
|
env:
|
|
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
|
|
jobs:
|
|
postRelease:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: checkout sources
|
|
uses: actions/checkout@v4
|
|
|
|
- name: atomically create or retrieve the build number and assemble release notes
|
|
id: version_number
|
|
run: |
|
|
bash -x ./scripts/get-atomic-buildnr.sh ${{ github.sha }} ${{ secrets.NIGHTLY_BUILDS }} "CICD-release"
|
|
bash scripts/create-releasenotes.sh ${{ github.event.head_commit.id }}
|
|
|
|
# ironically, we have to upload a file, otherwise this won't create a release with just the release notes
|
|
- name: publish release
|
|
uses: softprops/action-gh-release@v1
|
|
with:
|
|
tag_name: v$(<release-version)
|
|
repository: subsurface/nightly-builds
|
|
token: ${{ secrets.NIGHTLY_BUILDS }}
|
|
prerelease: false
|
|
files: gh_release_notes
|
|
body_path: gh_release_notes
|