• All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• The pull request is targeting the dev branch.
• The code has been validated to compile successfully by running go vet ./....
• The code has been formatted properly using go fmt ./....

Why

When JFrog CLI checks for the latest version, it calls the GitHub Releases API.
Without a token, these requests are anonymous and can quickly hit GitHub’s low rate limit, especially in CI.
This surfaced in the setup action as workflows intermittently failing due to HTTP 403 from the GitHub API (rate limit).

What’s changing

1. Tokenized version check

   • utils.CheckNewCliVersionAvailable(currentVersion) now reads JFROG_CLI_GITHUB_TOKEN from the environment and uses it as a Bearer token for the GitHub API request.
   • If absent, the call proceeds anonymously, but with clearer logging.

2. New env var

   • Introduce JFROG_CLI_GITHUB_TOKEN, documented in docs/common/env.go and surfaced in global env var help.

3. API & flags cleanup

   • Remove the app-level --github-token global flag and its plumbing from main.go.
   • Configuration via env var is now the single supported path.

Relates to :
jfrog/setup-jfrog-cli#223