#!/usr/bin/env sh
#
# The release tag that holds a channel's builds.
#
#   channel-tag.sh <dev|stable>
#
# A channel and its release tag are two different names, and for `dev` they differ.
# The channel is what a person picks and sees (`install.sh --channel dev`, the app's
# settings); the tag is where CI publishes and where every reader fetches from.
#
# A tag named `dev` would shadow the branch named `dev`: once a clone had fetched
# tags, `git push origin dev` would fail with "src refspec dev matches more than
# one". So the dev channel's tag is `dev-rolling`. Never spell a channel tag like a
# branch — tests/test_channel_tag.py fails if one is.
#
# The ONE mapping CI reads. Two copies exist because their readers cannot run this:
# `desktop/src-tauri/src/update.rs` (compiled into the app) and
# `desktop/packaging/install.sh` (fetched alone through a pipe). Change all three.
set -eu

case "${1:-}" in
  dev)    echo dev-rolling ;;
  stable) echo stable ;;
  *)
    echo "channel-tag.sh: unknown channel '${1:-}' (expected dev or stable)" >&2
    exit 2
    ;;
esac