Restrict releases to version tags
Some checks failed
Gitea Android APK / build (push) Failing after 0s
Gitea Smoke / smoke (push) Successful in 0s

This commit is contained in:
Codex 2026-07-06 12:43:11 +00:00
parent 67968654cb
commit 147cec7c6b
3 changed files with 8 additions and 26 deletions

View File

@ -8,15 +8,6 @@ on:
- "v*" - "v*"
pull_request: pull_request:
workflow_dispatch: workflow_dispatch:
inputs:
publish_release:
description: "Create or update a GitHub Release"
required: true
default: "false"
type: choice
options:
- "false"
- "true"
permissions: permissions:
contents: write contents: write
@ -25,7 +16,7 @@ jobs:
build: build:
runs-on: ubuntu-latest runs-on: ubuntu-latest
env: env:
PUBLISH_RELEASE: ${{ github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v') || inputs.publish_release == 'true' }} PUBLISH_RELEASE: ${{ github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v') }}
steps: steps:
- name: Checkout - name: Checkout
@ -139,15 +130,7 @@ jobs:
env: env:
GH_TOKEN: ${{ github.token }} GH_TOKEN: ${{ github.token }}
run: | run: |
if [[ "${GITHUB_REF}" == refs/tags/v* ]]; then
TAG="${GITHUB_REF_NAME}" TAG="${GITHUB_REF_NAME}"
else
TAG="v${VERSION_NAME}"
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
git tag -f "${TAG}"
git push -f origin "${TAG}"
fi
if gh release view "${TAG}" >/dev/null 2>&1; then if gh release view "${TAG}" >/dev/null 2>&1; then
gh release upload "${TAG}" release/tmux-android.apk release/latest.json --clobber gh release upload "${TAG}" release/tmux-android.apk release/latest.json --clobber
@ -157,4 +140,3 @@ jobs:
--title "tmux Android ${VERSION_NAME}" \ --title "tmux Android ${VERSION_NAME}" \
--notes "Android APK for tmux-ui remote testing." --notes "Android APK for tmux-ui remote testing."
fi fi

View File

@ -78,8 +78,8 @@ Create the base64 value from your release keystore:
base64 -w 0 tmux-android-release.jks base64 -w 0 tmux-android-release.jks
``` ```
Branch builds create Actions artifacts only. Use them to verify grouped changes Branch builds and manual workflow runs create Actions artifacts only. Use them
before publishing. to verify grouped changes before publishing.
Publish a release build by pushing a `v*` tag. A tag should be reserved for a Publish a release build by pushing a `v*` tag. A tag should be reserved for a
coherent feature/test batch, not every small UI or text change. Tag publishing coherent feature/test batch, not every small UI or text change. Tag publishing

View File

@ -110,10 +110,10 @@ install settings before the installer can run. After the user grants that
permission and returns to the app, the app resumes installation of the pending permission and returns to the app, the app resumes installation of the pending
APK instead of asking the user to run update again. APK instead of asking the user to run update again.
Only `v*` tags publish GitHub Releases. Main branch builds are for CI artifacts Only `v*` tags publish GitHub Releases. Main branch builds and manual workflow
and should be used to validate grouped changes. Do not publish a new tag for runs are for CI artifacts and should be used to validate grouped changes. Do not
every small UI copy or layout change; publish when there is a useful feature or publish a new tag for every small UI copy or layout change; publish when there
test batch for phone-side validation. is a useful feature or test batch for phone-side validation.
## Native Roadmap ## Native Roadmap