@duvoai/cli 0.2.0 → 0.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +42 -5
- package/dist/bin/duvo.js +3371 -2168
- package/dist/bin/duvo.js.map +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -97,11 +97,20 @@ duvo --profile team-2 whoami # one-off override for a single command
|
|
|
97
97
|
| `duvo files content-set <path>` | Update the content of a text file |
|
|
98
98
|
| `duvo files rename` | Rename a team file |
|
|
99
99
|
| `duvo files delete <path>` | Delete a team file |
|
|
100
|
-
| `duvo
|
|
101
|
-
| `duvo
|
|
102
|
-
| `duvo
|
|
103
|
-
| `duvo
|
|
104
|
-
| `duvo
|
|
100
|
+
| `duvo revisions list --agent <id>` | List revisions for an agent |
|
|
101
|
+
| `duvo revisions get <id> --agent <id>` | Get a revision by ID |
|
|
102
|
+
| `duvo revisions create --agent <id> --name <text>` | Create a new revision for an existing agent |
|
|
103
|
+
| `duvo revisions update <id>` | Update a revision's config (handover targets are derived from the SOP) |
|
|
104
|
+
| `duvo integrations list` | List the team's integration catalog |
|
|
105
|
+
| `duvo connections list` | List your connections (filter with `--type`) |
|
|
106
|
+
| `duvo connections get <id>` | Get one of your connections by ID |
|
|
107
|
+
| `duvo revision-integrations list` | List integrations attached to a revision |
|
|
108
|
+
| `duvo revision-integrations attach` | Attach one or more integrations to a revision |
|
|
109
|
+
| `duvo revision-integrations remove <integration-id>` | Remove an integration slot from a revision |
|
|
110
|
+
| `duvo revision-integrations connections list` | List your pinned connections for a revision's integration slot |
|
|
111
|
+
| `duvo revision-integrations connections pin <id>` | Pin one of your connections to a revision's integration slot |
|
|
112
|
+
| `duvo revision-integrations connections unpin <id>` | Unpin a connection from a revision's integration slot |
|
|
113
|
+
| `duvo plugins list` | List plugins referenceable by name in a revision |
|
|
105
114
|
| `duvo queues list` | List case queues for your team |
|
|
106
115
|
| `duvo queues get <id>` | Get a case queue by ID |
|
|
107
116
|
| `duvo queues create --name <name>` | Create a new case queue |
|
|
@@ -119,3 +128,31 @@ duvo --profile team-2 whoami # one-off override for a single command
|
|
|
119
128
|
| `duvo api <method> <path>` | Make a raw authenticated API request |
|
|
120
129
|
|
|
121
130
|
Run `duvo <command> --help` for full flags on any command.
|
|
131
|
+
|
|
132
|
+
## Publishing
|
|
133
|
+
|
|
134
|
+
The CLI is published to npm as [`@duvoai/cli`](https://www.npmjs.com/package/@duvoai/cli) via the [`Publish @duvoai/cli`](../.github/workflows/publish-duvo-cli.yml) GitHub Actions workflow.
|
|
135
|
+
|
|
136
|
+
### How to publish a new version
|
|
137
|
+
|
|
138
|
+
1. Bump `version` in `duvo-cli/package.json` (follow SemVer) and merge to the default branch.
|
|
139
|
+
2. Open the **Actions** tab → **Publish @duvoai/cli** → **Run workflow** and dispatch it from the default branch.
|
|
140
|
+
3. The workflow reads the version from `package.json`, skips if that version is already on npm, otherwise builds the CLI with prod Auth0 config baked in and publishes to npm.
|
|
141
|
+
|
|
142
|
+
### How the workflow works
|
|
143
|
+
|
|
144
|
+
- **Trigger:** manual `workflow_dispatch` only. There is no automatic publish on push or tag.
|
|
145
|
+
- **Auth:** OIDC trusted publishing to npm — no `NPM_TOKEN` is stored in the repo. The npm registry has a Trusted Publisher configured for `@duvoai/cli` pointing at this repo + workflow file. See [npm Trusted Publishers](https://docs.npmjs.com/trusted-publishers).
|
|
146
|
+
- **Idempotent:** `npm view @duvoai/cli@<version>` runs first; if the version already exists the build/publish steps are skipped, so re-running the workflow on an unchanged version is a no-op.
|
|
147
|
+
- **Concurrency:** the job uses `concurrency.group: publish-duvo-cli-${{ github.ref }}` with `cancel-in-progress: false`, so two near-simultaneous dispatches serialize instead of racing past the version check.
|
|
148
|
+
- **Auth0 config baked at build time:** the publish step sets `DUVO_CLI_DOMAIN=login.duvo.ai`, `DUVO_CLI_AUDIENCE=https://api.duvo.ai`, and `DUVO_CLI_CLIENT_ID=${{ secrets.DUVO_CLI_PROD_CLIENT_ID }}` so the published artifact targets the prod Auth0 tenant regardless of who runs `duvo login` and where.
|
|
149
|
+
|
|
150
|
+
### Required secrets
|
|
151
|
+
|
|
152
|
+
| Secret | Purpose |
|
|
153
|
+
| ------------------------- | ----------------------------------------------------------------- |
|
|
154
|
+
| `DUVO_CLI_PROD_CLIENT_ID` | Auth0 prod-tenant Client ID for the "Duvo CLI" Native application |
|
|
155
|
+
|
|
156
|
+
### Yanking a bad release
|
|
157
|
+
|
|
158
|
+
`npm publish` is append-only. To pull a broken version use `npm deprecate @duvoai/cli@<version> "<reason>"` (or in extreme cases, `npm unpublish` within the 72-hour window). Then bump the version in `package.json` and re-run the workflow.
|