-
Notifications
You must be signed in to change notification settings - Fork 609
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[rush] regression in rush update in 5.128.2 #4947
Comments
same issue when upgrade from |
Potential fix: #4992 (awaiting review at the moment) |
This should be fixed by #5057 which was released in 5.147.1, can you bump and see if it's fixed? |
Yes I believe this works! I'll file this separately, but I notice another issue with 5.147.1, between 5.147.0 and 5.147.1 for my top-level (usually globally-installed) rush I start seeing
But if I leave my top-level (usually globally-installed) version of rush where it was and just change my rush.json to use 5.147.1 I can see this working. |
Thanks for fixing @aramissennyeydd! |
filed #5064 |
In Rush 5.128.2 and beyond (probably from #4752?) the hashes for a project in a rush update never match so the shrinkwrap file always appears out of date.
See Zulip discussion
Summary
rush update
doesn't "resolve," every time I run it I getRepro steps
after adding a dependenciesMeta
running rush update twice should not produce
this should only happen the first time.
Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/rush
globally installed version?rushVersion
from rush.json?useWorkspaces
from rush.json?node -v
)?The text was updated successfully, but these errors were encountered: