Skip to content

Commit

Permalink
build(release): update release script
Browse files Browse the repository at this point in the history
Github has (it seems) updated the way to generate the `tar.gz` file.

I can't reverse engineer the way they do it, but they seem to do more
than just `git archive` now.
  • Loading branch information
jtheoof committed Nov 19, 2022
1 parent 689309b commit 6c410c0
Showing 1 changed file with 9 additions and 4 deletions.
13 changes: 9 additions & 4 deletions script/sign-post-release
Original file line number Diff line number Diff line change
Expand Up @@ -49,13 +49,15 @@ verify_sha256_checksums() {
sign_release_source() {
echo "signing source assets..."
cd $release_folder
gpg --output $app_name-$version.tar.gz.sig --detach-sign github-$app_name-$version.tar.gz
gpg --output $app_name-$version.tar.gz.sig --detach-sign local-$app_name-$version.tar.gz
}

upload_signed_assets_to_release() {
echo "uploading signatures to github release..."
echo "uploading signature and archive to github release..."
cd $release_folder
cp local-$app_name-$version.tar.gz $app_name-$version.tar.gz
gh release upload v$version $app_name-$version.tar.gz.sig --clobber
gh release upload v$version $app_name-$version.tar.gz --clobber
}


Expand All @@ -69,8 +71,11 @@ main() {
fi

build_archives_from_source
download_source_for_release
verify_sha256_checksums
# Turning off manual downloading from github
# It looks like the tar.gz from github is generated in a non-standard way
# but I couldn't find proper documenation on this
#download_source_for_release
#verify_sha256_checksums
sign_release_source
upload_signed_assets_to_release
}
Expand Down

0 comments on commit 6c410c0

Please sign in to comment.