replicatedhq / replicatedhq/replicated
"brew upgrade" suggestion can fail if user has not done "brew update"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 36
- Forks
- 25
- Avg merge
- 9h 27m
- Merged PRs (30d)
- 3
Description
I don't think Casks get updated as part of the regular auto-update that occurs during a brew upgrade - I have several times had to explicitly issue a brew update && brew upgrade replicatedhq/replicated/cli to get the CLI package to upgrade.
The suggestion from the binary should probably include something to that effect.
Today:
$ replicated cluster kubeconfig 8d9ae092
Update available: v0.70.0
To upgrade, run "brew upgrade replicatedhq/replicated/cli"
$ brew upgrade replicatedhq/replicated/cli
Warning: replicatedhq/replicated/cli 0.69.0 already installed
Should probably read:
To upgrade, run "brew update && brew upgrade replicatedhq/replicated/cli"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the Go source for the exact current text, "brew upgrade replicatedhq/replicated/cli", and trace where the upgrade suggestion is assembled. Update the suggested command to include brew update &&, then run the relevant CLI tests or reproduce the shown command to verify the wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100