Skip to content

Provide best-practice guidance for managing yarn.lock #1190

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Provide best-practice guidance for managing yarn.lock #1190

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c8313ea
Provide best-practice guidance for managing yarn.lock
gordonmessmer Mar 10, 2023
2231c86
Use the common "note" style.
gordonmessmer Mar 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Use the common "note" style.
  • Loading branch information
@gordonmessmer
gordonmessmer authored Mar 12, 2023
commit 2231c860073743cb532b14c0450504152abe2e03
3 changes: 1 addition & 2 deletions lang/en/docs/cli/upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,8 +94,7 @@ yarn upgrade --scope @angular
yarn upgrade -S @angular
```

Note:

**Note:**
Users should be aware that when yarn.lock is present, indirect dependencies
will only be updated by `yarn upgrade` without a package name. In order to
maintain the security of their applications, users should ensure that `yarn
Expand Down