-
Notifications
You must be signed in to change notification settings - Fork 76
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 recipes still pulling down v7 when v8 is out (though v7 updates are still coming) #222
Comments
Given that 1Password 8 is Electron-based and requires a subscription, whereas 1Password 7 is native code and still supports people who are grandfathered in without subscriptions and with local vaults, it might make sense to have a separate recipe for handling version 8. |
We should leave this recipe as it is as there are still might coming some v7 patches and v7 does still have standalone (non-subscription) licenses AgileBits renamed the App from "1Password 7" to "1Password" I made new "1Password latest" recipe as we needed to Deploy v8 |
i wrote a little sloppy pre-flight script for the 1Password 7 recipe to prevent overwriting of manual 1Password 8 installations;
|
I had a PR to update these recipes to work with 1Password 8+, but closed it since others have made recipes that accomplish this. I'd recommend this recipe be updated to specify that it only applies to 1Password 7. |
I think keeping it restricted to 1Password 7 is a fine idea; that's what we install here, as we have no policy in place to deal with the version 8 subscription mechanism. |
Subject line covers it.
Not sure what best approach is, but figured I would mention that 1Password v8 has been out for a short bit now. The current 1Password recipes are still aimed at v7. They did help to pull down the latest v7 patch on 18 May as the history shows.
Unfortunately, it does not look like you can just tweak the current URL in the download recipe from
to
as that doesn't exist.
Best I have found this page where they have a direct link to
if that helps.
The text was updated successfully, but these errors were encountered: