@qui-cli/env-1password 1.2.0 → 1.2.1

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to this project will be documented in this file. See [commit-and-tag-version](https://github.com/absolute-version/commit-and-tag-version) for commit guidelines.
 
+## [1.2.1](https://github.com/battis/qui-cli/compare/env-1password/1.2.0...env-1password/1.2.1) (2025-12-23)
+
+
+### Bug Fixes
+
+* fix crucial typo in documentation ([5fca554](https://github.com/battis/qui-cli/commit/5fca55433d9c8261122614c7786954bde779d63a))
+
 ## [1.2.0](https://github.com/battis/qui-cli/compare/env-1password/1.1.0...env-1password/1.2.0) (2025-12-23)
 
 

package/dist/1Password.js

@@ -56,7 +56,7 @@ export function options() {
                 text: 'Store 1Password secret references in your environment, rather than the actual secrets.'
             },
             {
-                text: `If 1Password secret references are stored in the environment, a 1Password service account token is required to access the secret values, which will be loaded into ${Colors.value('process.env')}. The service account token can be passed directly as the ${Colors.optionArg('--opToken')} argument (e.g. ${Colors.command(`${Colors.keyword('example')} --opToken "(${Colors.keyword('op')} item get myToken)"`)}) or, if the 1Password CLI tool is also installed, by simply passing the name or ID of the API Credential in your 1Password vault that holds the service account token (e.g. ${Colors.command(`${Colors.keyword('example')} --opItem myToken`)}). If you are signed into multiple 1Password account, use the ${Colors.optionArg('--opAccount')} argument to specify the account containing the token.`
+                text: `If 1Password secret references are stored in the environment, a 1Password service account token is required to access the secret values, which will be loaded into ${Colors.value('process.env')}. The service account token can be passed directly as the ${Colors.optionArg('--opToken')} argument (e.g. ${Colors.command(`${Colors.keyword('example')} --opToken "$(${Colors.keyword('op')} item get myToken)"`)}) or, if the 1Password CLI tool is also installed, by simply passing the name or ID of the API Credential in your 1Password vault that holds the service account token (e.g. ${Colors.command(`${Colors.keyword('example')} --opItem myToken`)}). If you are signed into multiple 1Password account, use the ${Colors.optionArg('--opAccount')} argument to specify the account containing the token.`
             },
             { text: Colors.url('https://developer.1password.com/docs/cli') }
         ],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qui-cli/env-1password",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "description": "@qui-cli Plugin: Standardized environment configuration",
   "homepage": "https://github.com/battis/qui-cli/tree/main/packages/env-1password#readme",
   "repository": {
@@ -28,10 +28,10 @@
     "del-cli": "^6.0.0",
     "npm-run-all": "^4.1.5",
     "typescript": "^5.9.3",
-    "@qui-cli/env": "5.0.2",
+    "@qui-cli/colors": "3.1.1",
     "@qui-cli/log": "4.0.1",
+    "@qui-cli/env": "5.0.2",
     "@qui-cli/plugin": "4.0.0",
-    "@qui-cli/colors": "3.1.1",
     "@qui-cli/root": "3.0.4",
     "@qui-cli/shell": "3.0.3"
   },