fix(cli): default all release builds to staging so the default install serves staging during testing

[tkkhq]

Tracking

• Tracks: https://konghq.atlassian.net/browse/VOL-519
• Related: fix: default CLI release builds to staging for testing phase #68 (this restores fix: default CLI release builds to staging for testing phase #68's original intent — default everything to staging)
• Related: feat(cli): parametrized staging release environment with dedicated release tag and package-manager coverage #90 (durable opt-in @staging channel, for GA when prod + staging coexist)

Summary

• default the CLI install to staging during the internal testing phase: production latest is not live yet, so the current default install is a broken production binary for new users
• build every release path against staging in scripts/ci/resolve-cli-build-env.sh — stable tags (which become GitHub latest and npm @latest) now bake https://api.staging.volcano.dev + the staging device client id, not just main/nightly
• keep it a deliberate, temporary swap: ponytail: comments mark the production blocks to restore before GA, and the production values are commented out so nothing bakes production during the phase
• update the publish-cli.yml comment so it is clear the staging device client id is now consumed by all release paths

Follow-up actions (not code)

• after merge, cut a stable release (e.g. v0.6.1) so GitHub latest + npm @latest flip to the staging build
• bump the Kong/homebrew-volcano volcano.rb formula to that release so brew install Kong/volcano/volcano serves staging too
• at GA: restore the production blocks, cut a production release, and adopt PR feat(cli): parametrized staging release environment with dedicated release tag and package-manager coverage #90's opt-in @staging channel

Verification

• bash -n scripts/ci/resolve-cli-build-env.sh
• python3 -c "import yaml; yaml.safe_load(open('.github/workflows/publish-cli.yml'))"
• simulated resolve-cli-build-env.sh for a stable tag (v0.6.1 -> api.staging.volcano.dev, staging client id), for main (nightly -> staging), and with the staging repo variable unset (fails naming VOLCANO_FIRST_PARTY_DEVICE_CLIENT_ID_STAGING)

[Copilot]

Pull request overview

Defaults all CLI release builds to staging during internal testing, ensuring stable, nightly, npm, and downstream installs use the working staging environment.

Changes:

• Bakes staging API, web URL, and OAuth client ID into every release path.
• Updates workflow guidance for restoring production configuration before GA.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
scripts/ci/resolve-cli-build-env.sh	Resolves stable and nightly builds to staging configuration.
.github/workflows/publish-cli.yml	Clarifies staging client ID usage across releases.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.