denoland/deno · error · AnyError

No {} release available at the moment.

Error message

No {} release available at the moment.

What it means

During an upgrade, Deno fetches the latest version for the target channel from dl.deno.dev. If that lookup fails with an error containing 'Not found', it means no build has been published for the requested channel yet, and Deno reports it with the channel's display name. Any other lookup error propagates unchanged.

Source

Thrown at cli/tools/upgrade.rs:1353

) -> Result<Option<AvailableVersion>, AnyError> {
  log::info!(
    "{}",
    colors::gray(&format!("Looking up {} version", release_channel.name()))
  );

  let client = http_client_provider.get_or_create()?;

  let latest_version_found = match fetch_latest_version(
    &client,
    release_channel,
    UpgradeCheckKind::Execution,
  )
  .await
  {
    Ok(v) => v,
    Err(err) => {
      if err.to_string().contains("Not found") {
        bail!(
          "No {} release available at the moment.",
          release_channel.name()
        );
      } else {
        return Err(err);
      }
    }
  };

  let current_version = match release_channel {
    ReleaseChannel::Canary => version::DENO_VERSION_INFO.git_hash,
    ReleaseChannel::Stable
    | ReleaseChannel::Lts
    | ReleaseChannel::Rc
    | ReleaseChannel::Alpha
    | ReleaseChannel::Beta => version::DENO_VERSION_INFO.deno,
  };
  let should_upgrade = force

View on GitHub (pinned to 9ad36f7a2c)

Solutions

1. Wait for the channel's first/current build to be published and retry.
2. If you need a specific version now, pin it explicitly (e.g. `deno upgrade v1.44.0`) or switch to the stable channel.
3. Check https://github.com/denoland/deno/releases to confirm the channel has shipped anything.
4. If you expected the channel to exist, verify you are on a recent Deno (channel names/URLs have changed across versions).

Example fix

# before
deno upgrade --rc  # no RC published yet -> error

# after
deno upgrade                 # stay on/bump stable
deno upgrade v1.44.0         # or pin an existing version

# confirm the channel has shipped before switching
curl -fsS https://dl.deno.land/release-latest-rc.txt >/dev/null || echo "no rc available yet — stay on stable"

deno upgrade --rc || deno upgrade  # fall back to stable if the channel has no release

When it happens

Trigger: `deno upgrade` targeting a channel (rc/alpha/beta/canary) whose latest metadata does not exist yet — e.g. the first RC cycle before any RC ships, or a canary window with no published build; the version endpoint returning 404 for that channel.

Common situations: Switching to `--rc`/`--beta` right after a release branch is cut but before artifacts publish; release-pipeline delays; requesting a channel that is currently dormant.

Related errors

• Failed to find PR #{pr_number}: {stderr}
• Failed to find CI runs for branch '{branch}': {stderr}
• Invalid commit hash passed ({}) Pass a semver, or a full 40
• Invalid version passed ({}) Pass a semver, or a full 40 cha
• Already upgraded

AI-assisted analysis of denoland/deno@9ad36f7a2c (2026-08-20). Data as JSON: /api/errors/ed184379e911d093. Report an issue: GitHub.