RustTube can optionally create GitHub releases directly from the build script.

This is handled through GitHub CLI (gh).

Before using release upload from the build script, make sure:

• GitHub CLI is installed
• GitHub CLI is authenticated
• you have access to the target repository
• the installer has already been built or is being built in the same workflow

Use build option 0 to verify that GitHub CLI is available and authenticated:

• 0 = Check GitHub CLI

This checks:

• whether gh is installed
• whether gh auth status succeeds

Build app package and installer.

After the installer is created, the script asks:

Create GitHub release v<version> and upload RustTube-Setup.exe? (y/n)

If you answer y, RustTube will:

• create a GitHub release for the current version tag
• upload RustTube-Setup.exe

Build installer only.

This also supports the same release prompt after the installer is created.

RustTube reads the version from Cargo.toml.

Example:

version = "1.1.6"

The GitHub release tag becomes:

v1.1.6

The uploaded installer file is:

dist\installer\RustTube-Setup.exe

The build script behaves like this:

• if the release tag already exists, it uploads or replaces the installer asset
• if the release tag does not exist, it creates a new release and uploads the installer

1. Run the build script
2. Choose option 2 or 3
3. Wait for the installer build to finish
4. When asked, enter y
5. The script creates or updates the GitHub release

• RustTube uses GitHub CLI instead of a custom API integration
• the release upload step is optional
• the release title uses the version tag
• generated release notes are enabled when creating a new release