1Password CLI 2.30.0

2.30.0
Added 2
  • Sensitive values in the human-readable output of item management commands are concealed and can be displayed using the --reveal flag.
  • Caching is used for service account sessions on macOS and Linux.
Changed 5
  • The error message shown when the CLI cannot connect with the 1Password desktop app now includes a link to troubleshooting documentation.
  • The op whoami command now signals whether the CLI is authenticated as a human user.
  • The output of op vault list now includes the created date and item count for each vault.
  • The op item move and op item delete commands now also work for SSH Key items.
  • The op vault revoke user command no longer allows revoking permissions in a Personal, Private, or Employee vault.
Fixed 1
  • When the same environment variable name exists in both the OS environment and the dotenv file, op run now correctly sources the value from the dotenv file.
Security 1
  • The Windows Authenticode signature now uses the SHA256 hashing algorithm.

From 1Password CLI

This release enables caching for service accounts and concealing sensitive information in the human readable output of items, as well as brings multiple other improvements and bug-fixes. Sensitive values from item management commands' human-readable output are now concealed and can be displayed using the --reveal flag. {4158} Caching is now being used for service account sessions on macOS and Linux. {4133} The error message when the CLI can't connect with the 1Password desktop app now includes a link to troubleshooting documentation for more help. {3933} op whoami will now signal if the CLI is authenticated as a human user. {4104} The output of op vault list now contains the created date and item count for each vault. {4092} The op item move and op item delete commands now also work for SSH Key items. {3951} The op vault revoke user command will no longer allow you to revoke permissions in a Personal, Private, or Employee vault. {3844} When the same environment variable name exists both in the OS environment and the dotenv file, op run now correctly sources the value from the dotenv file. {3667} Windows Authenticode signature now uses the SHA256 hashing algorithm. {4135}

View original

Upgraded? How did it go?

Discussion