Files
openswarm/publish.sh
T

43 lines
1.6 KiB
Bash
Executable File

#!/bin/bash
# The comment above is shebang, DO NOT REMOVE
#
# Publishes a macOS build to GitHub Releases. Channel is auto-detected from
# the semver string in electron/package.json:
#
# Stable: "1.0.37" -> normal GitHub release
# Experimental: "1.0.37-exp.1" -> marked Pre-release on GitHub; only reaches
# users with "Experimental updates" enabled
# in Settings > Advanced.
#
# To promote an experimental release to stable: un-check "This is a pre-release"
# on the GitHub release page (native GitHub UI, no code change needed).
#
# Windows release: tag-triggered via .github/workflows/release-windows.yml,
# which performs the same auto-detection.
PUBLISH_ABSPATH="$(readlink -f "${BASH_SOURCE[0]}")"
if [[ "$OSTYPE" == "darwin"* ]]; then
sed -i '' 's/\r//g' "$PUBLISH_ABSPATH"
else
sed -i 's/\r//g' "$PUBLISH_ABSPATH"
fi
chmod +x "$PUBLISH_ABSPATH"
PROJECT_ROOT="$(dirname "$PUBLISH_ABSPATH")"
cd "$PROJECT_ROOT"
# electron-builder auto-detects prerelease from semver suffix in electron/package.json
# (e.g. "1.0.37-exp.1" publishes as GitHub Pre-release; "1.0.37" publishes as stable).
# We also export EP_PRE_RELEASE for belt-and-suspenders so the GitHub Releases publisher
# can't accidentally promote an experimental build.
VERSION="$(node -p "require('./electron/package.json').version")"
if [[ "$VERSION" == *-* ]]; then
export EP_PRE_RELEASE=true
echo "==> Publishing EXPERIMENTAL release: v$VERSION (will be marked Pre-release on GitHub)"
else
echo "==> Publishing STABLE release: v$VERSION"
fi
bash scripts/build-app.sh --publish
cd -