Update SHA256 ARM hash for 1password

[b-h-mck]

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

---

SHA256 hash for 1password 8.10.74 ARM is wrong for some reason -- possibly a new package was uploaded with the same version number. I have updated it with the correct value (which I also double-checked against the package)

[khipp]

Thank you, @b-h-mck!

[complexspaces]

Hey everyone, I'm an engineer over at 1Password,

The release team investigated this issue this morning as part of a larger set of behavior issues. We confirmed that nothing "bad" happened and the hash changing was a result of accidentally publishing two builds, with different patch numbers, under the same filename by mistake. This error resulted in a bunch of weird side effects including returning different builds for the same number (which broke Homebrew). We're very sorry about the churn.

Later today a 8.10.75 release should be coming out that will smooth over the issues by giving the CDN a correctly matching version number/filename artifact. We'd recommend updating the cask to that build once its available to avoid future inconsistencies and CDN oddities.

[p-linnane]

Confirming @complexspaces is from 1Password. Thanks for the confirmation!