-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
1password: migrate casks (1) #172357
1password: migrate casks (1) #172357
Conversation
@@ -16,8 +16,6 @@ | |||
regex(%r{href=.*?/op_apple_universal[._-]v?(\d+(?:\.\d+)+)\.pkg}i) | |||
end | |||
|
|||
conflicts_with cask: "1password-cli1" |
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.
Why do these need to be removed and not changed?
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.
@bevanjkay, they're added back in #172356. The conflicting casks are not resolved in CI (See, e.g., https://github.com/Homebrew/homebrew-cask/actions/runs/8863512074/job/24337653300) and this is a workaround to migrating casks individually.
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.
The gather cask information
step is loading the casks from the API, so even after a rebase, it would continue to fail until the API propagates.
It might be better to have a way to switch the gather cask information
step to include the HOMEBREW_NO_INSTALL_FROM_API
environment variable.
Can you help here @Bo98?
39d18d2
to
3980305
Compare
Removing
conflicts_with cask
from this migration, will add back in a separate PR.The merge order is: