[dgitman]

Overview

zapier-platform-cli v19 dropped the zapier binary and only installs zapier-platform (v18 shipped both, with zapier deprecated). The plugin only registered zapier, so op plugin run -- zapier ... fails with 'zapier' cannot be found in $PATH for anyone on v19.

This adds a second executable for zapier-platform that uses the same Deploy Key credential and needs-auth rules. The existing zapier executable is unchanged.

Type of change

• Created a new plugin
• Improved an existing plugin
• Fixed a bug in an existing plugin
• Improved contributor utilities or experience

Related Issue(s)

• Resolves: #
• Relates: #

How To Test

With zapier-platform-cli@19: op plugin init zapier-platform, then zapier-platform --version / zapier-platform login.

Note: I haven't compiled or run the Go tests locally (no Go toolchain on my machine); relying on CI.

Changelog

The Zapier plugin now supports the zapier-platform binary installed by zapier-platform-cli v19.

🤖 Generated with Claude Code

[github-actions]

⚠️ This PR contains unsigned commits. To get your PR merged, please sign those commits (git rebase --exec 'git commit -S --amend --no-edit -n' @{upstream}) and force push them to this branch (git push --force-with-lease).

If you're new to commit signing, there are different ways to set it up:

Sign commits with gpg

Follow the steps below to set up commit signing with gpg:

1. Generate a GPG key
2. Add the GPG key to your GitHub account
3. Configure git to use your GPG key for commit signing

Sign commits with ssh-agent

Follow the steps below to set up commit signing with ssh-agent:

1. Generate an SSH key and add it to ssh-agent
2. Add the SSH key to your GitHub account
3. Configure git to use your SSH key for commit signing

Sign commits with 1Password

You can also sign commits using 1Password, which lets you sign commits with biometrics without the signing key leaving the local 1Password process.

Learn how to use 1Password to sign your commits.