PATH not configured after `midenup install stable` on Ubuntu

[Alice699]

Packages versions

midenup: 0.1.0
active toolchain: 0.20.3
miden-protocol: 0.13.3
OS: Ubuntu (Linux)
Shell: bash

Bug description

After midenup install stable completes successfully, running
miden --version returns "miden: command not found".

What happened: midenup installs binaries to
~/.local/share/midenup/bin/ but does not add this path to PATH
automatically. The installation appears successful but the binary
is unreachable.

What should have happened: Either midenup should configure PATH
automatically during installation, or the installation guide should
document this manual step.

Fix that worked:
echo 'export PATH="/home/USERNAME/.local/share/midenup/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

This fix is not documented anywhere in the official docs.

How can this be reproduced?

1. Install Rust via rustup
2. Run: cargo install midenup
3. Run: midenup init
4. Run: midenup install stable (wait ~45 minutes)
5. Run: miden --version

Result: "miden: command not found"

Relevant log output

miden: command not found

[Alice699]

[PhilippGackstatter]

I have a related issue now:

Docs at https://docs.miden.xyz/builder/get-started/setup/installation/ suggest adding .../midenup/bin to $PATH, but that directory doesn't exist when I did cargo install midenup (midenup + miden version: 0.2.0.)

I added $HOME/.local/share/midenup/toolchains/stable/bin instead, but it does not contain a miden executable, so which miden returns $HOME/.cargo/bin/miden.

The docs suggest this should return a path from the midenup directory, so that confused me.

midenup warning

Unrelated to this issue, but when creating a new project using miden new miden-bank, the following warning is issued:

WARNING: new is an alias from component cargo-miden, which is installed but is not part of the current active toolchain.

So it feels like I'm doing something wrong, but is there anything wrong?