@roarkanalytics/cli 0.31.1 → 0.32.1

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.32.1](https://github.com/roarkhq/cli-roark-analytics/compare/v0.32.0...v0.32.1) (2026-09-30)
+
+
+### Bug Fixes
+
+* **auth:** `auth status` reports the project a user credential already falls back to ([#81](https://github.com/roarkhq/cli-roark-analytics/issues/81)) ([4274667](https://github.com/roarkhq/cli-roark-analytics/commit/427466763aac7cf8144c455d3a2c78c1ba91ae03))
+
+## [0.32.0](https://github.com/roarkhq/cli-roark-analytics/compare/v0.31.1...v0.32.0) (2026-09-29)
+
+
+### Features
+
+* **cli:** cli update ([#79](https://github.com/roarkhq/cli-roark-analytics/issues/79)) ([9147caa](https://github.com/roarkhq/cli-roark-analytics/commit/9147caab0016324dd5307014257ca497e32aaaac))
+
 ## [0.31.1](https://github.com/roarkhq/cli-roark-analytics/compare/v0.31.0...v0.31.1) (2026-09-29)
 
 

package/README.md

@@ -40,28 +40,6 @@ a stored or environment credential to it. Pass `--allow-project-base-url` (or se
 `ROARK_ALLOW_PROJECT_BASE_URL`) once you have read the file, or `--token` to send a
 different credential.
 
-## Choose a project
-
-`auth login` gives you a credential that acts as you, and it can reach every project
-you belong to. So commands need to know which project they act on. The login writes
-the project you picked on the consent screen, and after that there is nothing to do:
-
-```sh
-roark config set project <project-id>   # change it
-roark config get project                # see it
-roark agent list --project <id>         # just this once
-export ROARK_PROJECT_ID="..."           # or for a shell
-```
-
-Precedence is the usual one: `--project`, then `ROARK_PROJECT_ID`, then `.roark.json`,
-then the user config. Committing `{"project": "..."}` in a repository's `.roark.json`
-is the intended way to pin a checkout to one project, and unlike `baseURL` it needs no
-opt-in: a project id chooses which of your own projects you act on, it cannot send your
-credential anywhere new.
-
-If you authenticate with a **project API key** instead, the key already names its
-project and all of this is ignored.
-
 ## Usage
 
 Commands read noun before verb, and the verb is one of `list`, `get`, `create`,

package/commands.js

@@ -1796,7 +1796,7 @@ exports.COMMANDS = [
         httpMethod: 'post',
         httpPath: '/v1/config/apply',
         summary: 'Apply a config bundle',
-        description: 'Reconcile a config-as-code bundle into the project. Submit the full desired set of resources; resources already managed by config are updated, new ones created, and (unless prune is false) config-managed resources absent from the bundle are deleted. Identity is by name — no ids in the bundle.',
+        description: 'Reconcile a config-as-code bundle. With a PROJECT API key, submit project-scoped resources (agents, personas, flows, collectors, metrics, ...). With an ORGANIZATION API key, submit `kind: project` resources, each optionally carrying its members and its own nested `resources`. Submit the full desired set; managed resources are updated, new ones created, and (unless prune is false) managed resources absent from the bundle are deleted. Identity is by name.',
         positionals: [],
         flags: [
             {
@@ -1830,7 +1830,7 @@ exports.COMMANDS = [
         httpMethod: 'post',
         httpPath: '/v1/config/diff',
         summary: 'Diff a config bundle',
-        description: 'Dry run for a config-as-code apply: returns the projected changes (create / update / delete) for the submitted bundle without writing anything. Submit the full desired set of resources; identity is by name — no ids in the bundle. Run this before apply to preview what would change.',
+        description: 'Dry run for an apply: returns the projected changes (create / update / delete) for the submitted bundle without writing anything. Works for both project and organization keys.',
         positionals: [],
         flags: [
             {

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@roarkanalytics/cli",
-  "version": "0.31.1",
+  "version": "0.32.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@roarkanalytics/cli",
-      "version": "0.31.1",
+      "version": "0.32.1",
       "license": "Apache-2.0",
       "dependencies": {
         "@roarkanalytics/sdk": "^4.15.0",
@@ -21,9 +21,9 @@
       }
     },
     "node_modules/@roarkanalytics/sdk": {
-      "version": "4.15.0",
-      "resolved": "https://registry.npmjs.org/@roarkanalytics/sdk/-/sdk-4.15.0.tgz",
-      "integrity": "sha512-H5bHFILsMVMUG7+6yi3gO4JrAvvoFPLn82zZp0tS1A6UugH/hzQgwuMFSkjbJCl29p9GcVjAFhLDaZa7845gmA==",
+      "version": "4.18.0",
+      "resolved": "https://registry.npmjs.org/@roarkanalytics/sdk/-/sdk-4.18.0.tgz",
+      "integrity": "sha512-+s6s6Owxqe/Mvh6/7TkNbYcVtsrdjYYciRrpinTSURliSnM+T63XWZW0lkEuIvn4d+Y/BTbNDtRtP14aCpw72A==",
       "license": "Apache-2.0"
     },
     "node_modules/commander": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@roarkanalytics/cli",
-  "version": "0.31.1",
+  "version": "0.32.1",
   "description": "The official command line interface for the Roark API",
   "author": "Roark <james@roark.ai>",
   "type": "commonjs",

package/runtime/commands/auth.js

@@ -58,7 +58,12 @@ const describeCredential = async (clientFor) => {
     };
     try {
         const me = (await client.get(AUTH_DESCRIBE_PATH));
-        return { kind: 'live', scope: me.data?.tokenScope, email: me.data?.user?.email ?? null };
+        return {
+            kind: 'live',
+            scope: me.data?.tokenScope,
+            email: me.data?.user?.email ?? null,
+            ...(me.data?.defaultProject?.id ? { defaultProject: me.data.defaultProject.id } : {}),
+        };
     }
     catch (error) {
         if (error.status !== 404)
@@ -275,10 +280,19 @@ const registerAuthCommands = (root, binaryName, clientFor) => {
             if (state.scope === 'USER') {
                 // A user credential reaches every project you belong to, so which one it acts on is part
                 // of the answer, not a detail.
+                //
+                // Three cases, not two. A locally configured project wins; failing that the credential's
+                // own default is what the API will use, and saying "commands will fail" there would be
+                // plainly wrong (they succeed). Only a credential with neither is actually stuck.
                 const project = (0, config_1.loadConfig)().project;
-                (0, output_1.write)((0, output_1.paint)(project ?
+                const message = project ?
                     `Acting on project ${project}. Change it with \`${binaryName} config set project <id>\`.`
-                    : `No project selected: commands will fail until you set one with \`${binaryName} config set project <id>\`.`, 'dim', color), process.stderr);
+                    : state.defaultProject ?
+                        `Acting on project ${state.defaultProject}, the default stored on this credential. ` +
+                            `Override it with \`${binaryName} config set project <id>\`.`
+                        : `No project selected, and this credential has no default: project commands will fail until ` +
+                            `you run \`${binaryName} config set project <id>\`. \`${binaryName} project list\` shows the ids.`;
+                (0, output_1.write)((0, output_1.paint)(message, 'dim', color), process.stderr);
             }
         }
         if (fromEnv && stored) {

package/version.d.ts

@@ -1 +1 @@
-export declare const version = "0.31.1";
+export declare const version = "0.32.1";

package/version.js

@@ -10,4 +10,4 @@ exports.version = void 0;
 //
 // Do not edit: an edit here is overwritten, and the published number is whatever
 // package.json says.
-exports.version = '0.31.1'; // x-release-please-version
+exports.version = '0.32.1'; // x-release-please-version