Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

espup reports 0.18.0 is available, even though it's not

Open Beginner friendly
#596 0 comments 0 reactions 0 assignees View on GitHub

@SergioGasquez is already working on this.

Since Oct 23, 2026.

  • #597 by @SergioGasquez — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
cli, release

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 bug jury

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:

  1. Run cargo install espup --locked according to the documentation
  2. 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

Image

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

Open in Codespaces

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from esp-rs/espup

All issues in esp-rs/espup

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.