In Deno 2.3.0, the version was accidentally released as `2.4.0`. This was fixed in 2.3.1. Now anyone who upgraded to 2.3.0 can't run `deno upgrade` to upgrade to 2.3.1 because of this upgrade behaviour. It would be better to just always go to the latest remote specified version when someone runs `deno upgrade`. This also fixes a bug outlined in https://github.com/denoland/deno/issues/29016 Closes https://github.com/denoland/deno/issues/29016
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by dsherret and has received 0 comments.