@duvoai/cli 0.3.0 → 0.3.1

package/README.md

@@ -128,31 +128,3 @@ duvo --profile team-2 whoami   # one-off override for a single command
 | `duvo api <method> <path>`                                                           | Make a raw authenticated API request                                                    |
 
 Run `duvo <command> --help` for full flags on any command.
-
-## Publishing
-
-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.
-
-### How to publish a new version
-
-1. Bump `version` in `duvo-cli/package.json` (follow SemVer) and merge to the default branch.
-2. Open the **Actions** tab → **Publish @duvoai/cli** → **Run workflow** and dispatch it from the default branch.
-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.
-
-### How the workflow works
-
-- **Trigger:** manual `workflow_dispatch` only. There is no automatic publish on push or tag.
-- **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).
-- **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.
-- **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.
-- **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.
-
-### Required secrets
-
-| Secret                    | Purpose                                                           |
-| ------------------------- | ----------------------------------------------------------------- |
-| `DUVO_CLI_PROD_CLIENT_ID` | Auth0 prod-tenant Client ID for the "Duvo CLI" Native application |
-
-### Yanking a bad release
-
-`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.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@duvoai/cli",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Command-line interface for the Duvo public API",
   "bin": {
     "duvo": "./dist/bin/duvo.js"