Skip to content

Add Expo plugin with expo and eas CLI support#563

Merged
scottisloud merged 2 commits into
1Password:mainfrom
CodeByZach:add-expo-plugin
Jun 22, 2026
Merged

Add Expo plugin with expo and eas CLI support#563
scottisloud merged 2 commits into
1Password:mainfrom
CodeByZach:add-expo-plugin

Conversation

@CodeByZach

Copy link
Copy Markdown
Contributor

Overview

Adds a shell plugin for Expo, supporting both the expo and eas CLIs. Authentication is handled via the EXPO_TOKEN environment variable using access tokens generated from the Expo dashboard.

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

  1. Generate an access token at https://expo.dev/accounts/[account]/settings/access-tokens
  2. Build the plugin locally: make expo/build
  3. Initialize: op plugin init expo
  4. Test authentication: expo whoami

Changelog

Authenticate the Expo and EAS CLIs using 1Password Shell Plugins.

@CodeByZach

Copy link
Copy Markdown
Contributor Author

Friendly follow up
@kmk142789
@edif2008
@Marton6
@volodymyrZotov
@SimonBarendse

@zachary-onix

zachary-onix commented Feb 12, 2026

Copy link
Copy Markdown

Kindly following up
@AndyTitu
@edif2008
@volodymyrZotov

@zachary-onix

Copy link
Copy Markdown

@scottisloud

@scottisloud scottisloud left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your patience on this one — sorry it's taken a while to get back to you.

I've reviewed the Expo plugin and it looks ready to merge. EXPO_TOKEN is the right env var for both expo and eas per Expo's programmatic access docs, the auth gating on both executables is appropriate, and the provisioner/importer tests are in good shape.

Approved — I'll merge once you've rebased onto current main and CI is green. Thanks, @CodeByZach.

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ 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.

Watch the demo

@scottisloud scottisloud left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for bringing the PR up to date! LGTM!

Keep an eye out for this to be included in a future release of the 1Password CLI. Thanks again for your contribution @CodeByZach!

@scottisloud scottisloud merged commit f683267 into 1Password:main Jun 22, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants