yarnpkg/yarn

yarn upgradeInteractive --latest not showing latest package(s)

Open

#6852 opened on Dec 25, 2018

View on GitHub
 (10 comments) (7 reactions) (1 assignee)JavaScript (41,514 stars) (2,731 forks)batch import
cat-buggood first issuehelp wanted

Description

Do you want to request a feature or report a bug? bug

What is the current behavior? yarn upgradeInteractive --latest doesn't seem to show the latest package versions, or I'm missing out something? For example, "react": "^16.6.3", in package.json, while react@16.7.0 is already available?

I was able to successfully use the command some hours before to update some really old packages. I also tried to delete the node_modules directory incl. yarn.lock file, which unfortunately didn't help to resolve this issue.

$ yarn upgradeInteractive --latest
yarn upgradeInteractive v1.12.3
success All of your dependencies are up to date.
Done in 0.56s.

If the current behavior is a bug, please provide the steps to reproduce.

Please see above.

What is the expected behavior? I would expect it to offer an upgrade to react@16.7.0 which can be added separately.

Please mention your node.js, yarn and operating system version. Node.js: 8.11.3 Yarn: 1.12.3 OS: Windows 10

Contributor guide

Tech stack
javascriptnodejs
Domain
cli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptNode.jsYarn CLI architecturepackage registry
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Start by examining the upgrade interactive command logic in `src/cli/commands/upgrade interactive.js`. Investigate how the latest version is fetched from the registry, possibly using `yarn check` or the npm API. Look for caching mechanisms that might prevent refreshing the version list. Check comments in the issue for any hints from maintainers about the root cause.