espup reports 0.18.0 is available, even though it's not
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
Research direction
Start by tracing how espup install determines the latest available version and how the release version is published; the issue identifies the command and the expected version as 0.17.1. Check the version lookup and release configuration, then reproduce with the documented cargo install espup --locked command. Done when the installed version no longer reports a nonexistent v0.18.0.
Written by the indexing model from the issue text.
Description
Bug description
The instructions say to run cargo install espup --locked to install, which will build the latest available version. That is currently 0.17.1. Actually running espup reports there is a v0.18.0 available.
To Reproduce
Steps to reproduce the behavior:
- Run
cargo install espup --lockedaccording to the documentation - Run
espup install
Expected behavior
The latest version should be installed, and the actual command shouldn't say to install a version that doesn't exist.
Screenshots
Environment
- OS: macOs 26.5.2 (25F84)
- espup version: 0.17.1
- Dominant language
- Rust
- Stars
- 461
- Forks
- 37
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 7
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from esp-rs/espup
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Toolchain installation fails with "GitHub API returned status code: 401 Unauthorized"Possibly taken @SergioGasquez claimed this 2 days ago. Openbug bug jury
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
enhancement feature request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
area/backends bug session-analysis
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
docs good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
crash
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
aaif-goose/goose#13125 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day