-
Notifications
You must be signed in to change notification settings - Fork 5k
Remove use of --no-lock with Homebrew. #113277
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Overview
This PR updates the Homebrew installation instructions by removing the obsolete --no-lock flag, which is no longer needed following changes in Homebrew Bundle.
- Removed the --no-lock option from the brew bundle command in the macOS requirements documentation.
Reviewed Changes
File | Description |
---|---|
docs/workflow/requirements/macos-requirements.md | Updated command to remove the deprecated --no-lock flag. |
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
Tip: Copilot code review supports C#, Go, Java, JavaScript, Markdown, Python, Ruby and TypeScript, with more languages coming soon. Learn more
Thanks, please also open in arcade so it's not overwritten by the next arcade update. 🙂 |
Homebrew removed lock file generation in Homebrew/homebrew-bundle#1509, and left
--no-lock
as a no-op. It was removed entirely in Homebrew/homebrew-bundle@98d8ad7, which causes errors when passing this option.Associated arcade PR: dotnet/arcade#15608
Closes #113276