BigskyTranferFiles includes an internal update flow to reduce manual rollout effort when distributing new versions across multiple Windows machines.

This update model is especially useful when the repository is used primarily as a binary release repository rather than a source-code collaboration repository.

• Local folder
• UNC or network share
• Direct manifest URL
• GitHub repository URL
• GitHub Releases manifest URL

• Shows the version currently running on the machine

• Stores the update channel location
• Accepted values include:
  • local folder path
  • network share path
  • direct manifest URL
  • GitHub repository URL

• When enabled, the app automatically checks for updates when Server Screen opens

• Opens a folder picker for local or network-share update feeds
• Not used for GitHub URLs

• Performs an immediate update check

• Becomes meaningful when a newer version is found
• Downloads the new Setup.exe locally and launches the installer

• Clears the stored update feed

• Displays the latest version discovered in the configured update channel

The app supports:

https://github.com/<owner>/<repo>

When that format is entered, the app resolves it to:

https://github.com/<owner>/<repo>/releases/latest/download/BigskyTranferFiles.update.json

The app also supports:

https://github.com/<owner>/<repo>/releases/latest/download/BigskyTranferFiles.update.json

• BigskyTranferFiles-Setup-<version>.exe
• BigskyTranferFiles.update.json

The manifest must point to the correct installer asset for that release.

These two files are the core release deliverables for update consumption.

build-release.cmd

powershell -ExecutionPolicy Bypass -File .\scripts\publish-github-release.ps1 `
  -Repository "<owner>/<repo>"

The script will:

• rewrite BigskyTranferFiles.update.json with the correct GitHub asset URL
• create the release if it does not exist
• upload Setup.exe
• upload BigskyTranferFiles.update.json

After that, the desktop application can use the GitHub release as its update feed without requiring a shared local folder.

• The repository must contain at least one commit
• The token must have:
  • Contents: Read and write
  • Metadata: Read-only

The repository has no commits yet. Push at least one commit before creating releases.

The token does not have sufficient permissions. Verify that Contents: Read and write is enabled.

For clean internal rollout:

1. build the installer
2. publish a GitHub Release
3. upload Setup.exe and BigskyTranferFiles.update.json
4. point clients to the repository URL or the direct manifest URL