Skip to content

Releases: pima-io/pima-cli

v0.6.0

10 Jun 03:34
v0.6.0
46c378b

Choose a tag to compare

What Changed

  • Added guardrails for the legacy sales_report JSON payload: pima report get sales_report now fails with an actionable metrics sales replacement instead of returning the scaffold-only report payload.
  • MCP pima_report applies the same sales_report guard so agents are steered to pima_sales_summary for sales totals.

Verification

  • npm run prepack
  • npm run lint:skills
  • isolated npm test
  • npm pack dry-run with temp cache
  • npm registry verified latest: 0.6.0

v0.5.0

09 Jun 21:34
v0.5.0
fc9f854

Choose a tag to compare

What's new

  • Add pima update to install the latest published CLI with npm install -g @pima-io/cli@latest.
  • Add pima update --dry-run so agents and users can inspect the exact install command before running it.
  • Document update flow in the README and bundled getting-started skill.

Validation

  • npm run build
  • npm run lint:skills
  • npm test
  • npm --cache /private/tmp/pima-cli-npm-cache pack --dry-run
  • ./bin/dev.js update --dry-run
  • npm registry verified: latest is 0.5.0.

v0.4.0

09 Jun 15:30
v0.4.0
b4ee470

Choose a tag to compare

What's new

  • Added pima questions, a first-class command for example business questions and optimized command mappings.
  • Added --match, --category, and --json output for agent-friendly question discovery.
  • Added the MCP pima_question_catalog tool so agents can call the catalog before sales, product, team, inventory, routing, audit, and compound metric questions.
  • Added post-login and skill-listing hints that point agents toward pima questions, pima skill getting-started, and pima skill --all.

Verification

  • npm run prepack
  • npm run lint:skills
  • npm test
  • pima questions --match "who sold tshirts"
  • npm pack --dry-run

v0.3.1

09 Jun 03:53
v0.3.1
ba37050

Choose a tag to compare

Changes

  • Adds OAuth refresh-token support for CLI device-flow sessions.
  • Refreshes stored tokens before expiry and retries once after a 401 response.
  • Updates pima auth status to report whether the current session is refreshable.

Server compatibility

PIMA production now issues refresh tokens for new CLI device-flow logins. Existing sessions minted before the server deploy need one fresh pima auth login; after that, the CLI can keep the session alive automatically.