v2.0.2 self-reports as 2.0.1, causing a permanent "outdated version" warning
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 245
- Forks
- 41
- Avg merge
- 28m
- Merged PRs (30d)
- 1
Description
Description
The v2.0.2 tag still has 'version' => '2.0.1' in config/app.php — the version bump was missed when tagging:
https://github.com/laravel/forge-cli/blob/v2.0.2/config/app.php#L36
As a result, on a fresh install of the latest release:
$ composer global show laravel/forge-cli | grep versions
versions : * v2.0.2
$ forge --version
Forge CLI 2.0.1
And every authenticated command prints the update warning permanently, since the self-check compares the internal version string against Packagist:
==> You Are Using An Outdated Version [v2.0.1] Of Forge CLI. Please Update To [v2.0.2].
Suggested fix
Bump the version in config/app.php, rebuild builds/forge, and tag v2.0.3.
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
Start with config/app.php at the version setting referenced in the issue, then inspect the existing builds/forge release artifact and the forge --version entry point. Done means the next tagged release reports its own version and no longer triggers the outdated-version warning; the issue specifically suggests rebuilding builds/forge and tagging v2.0.3.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100