yarnpkg / berry

📦🐈 Active development trunk for Yarn ⚒
https://yarnpkg.com
BSD 2-Clause "Simplified" License
7.43k stars 1.11k forks source link

[Bug] Unexpected update prompt with interactive-tools plugin #2580

Open suiyun39 opened 3 years ago

suiyun39 commented 3 years ago

Describe the bug

For package @docusaurus/core. The package latest version is 2.0.0-alpha.70, in my workspace is already upgraded to this version. But interactive-tools plugin prompt:

@docusaurus/core ◉ ^2.0.0-alpha.… ◯ ^2.0.0

I think this is a mistake

To Reproduce

The repo provides a minimum reproducibility: https://github.com/NoDocCat/yarn2-issue-repo You can run yarn install, then run yarn upgrade-interactive.

Screenshots

The package on npm: image

My workspace package.json: image

Results of the plugin image

Environment if relevant (please complete the following information):

Additional context

How can i import interactive-tools plugin in sherlock

yarnbot commented 3 years ago

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

F3n67u commented 2 years ago

I encounter the same problem.

F3n67u commented 2 years ago

I encounter the same problem.

I will be very happy to contribute to this fix.