<!-- @generated by usage-cli from usage spec -->
# `mise ls-remote`

- **Usage**: `mise ls-remote [FLAGS] [TOOL@VERSION] [PREFIX]`
- **Effect**: read-only
- **Source code**: [`src/cli/ls_remote.rs`](https://github.com/jdx/mise/blob/main/src/cli/ls_remote.rs)

List runtime versions available for install.

Note that the results may be cached, run `mise cache clean` to clear the cache and get fresh results.

## Arguments

### `[TOOL@VERSION]`

Tool to get versions for

### `[PREFIX]`

The version prefix to use when querying the latest version
same as the first argument after the "@"

## Flags

### `--all`

Show all installed plugins and versions

### `--minimum-release-age <MINIMUM_RELEASE_AGE>`

Only show versions released before this age or date

Supports absolute dates like "2024-06-01" and relative durations like "90d" or "1y".

### `-J --json`

Output in JSON format (includes version metadata like created_at timestamps when available)

### `--no-versions-host`

Disable checking the mise-versions host

### `--prerelease`

Include pre-release versions in the output for backends that report
upstream prerelease metadata or opt in to regex-based prerelease
detection. Equivalent to setting `MISE_PRERELEASES=1` or the
`prereleases` setting for the duration of this command.

### `--strict-metadata`

Fail if release metadata fetches fail

Requires --json and --no-versions-host.

This prevents metadata consumers from accepting empty fallback results
when a backend's metadata-producing upstream request fails.

Examples:

```
$ mise ls-remote node
18.0.0
20.0.0

$ mise ls-remote node@20
20.0.0
20.1.0

$ mise ls-remote node 20
20.0.0
20.1.0

$ mise ls-remote node --minimum-release-age 2024-01-01
20.0.0

$ mise ls-remote github:cli/cli --json
[{"version":"2.62.0","created_at":"2024-11-14T15:40:35Z","prerelease":false},{"version":"2.61.0","created_at":"2024-10-23T19:22:15Z","prerelease":false}]
```
