chore(release): cli 0.2.7 + docs + Mintlify auto-deploy workflow

Wraps up the AGENTRUSH CLI release across both clients.

Lint:
- Node Biome: collapse multi-line printError() in whoami.ts
- Python ruff: drop unused BRAND_COLOR import; replace EN DASH with
  HYPHEN-MINUS in app.py docstring

Release:
- Bump @mem0/cli and mem0-cli from 0.2.6 → 0.2.7 (patch)
- Add CHANGELOG.md (Keep a Changelog format) to both CLIs, seeded
  with the 0.2.7 entry covering whoami, agent-rush <add|search>, the
  PII safety prompt, and the new agent_rush.acknowledged_at config field

Docs:
- docs/platform/cli.mdx: new sections for `mem0 whoami` and
  `mem0 agent-rush <add|search>` with rule table, error-code hints,
  the launch copy-paste block, and the public-memory warning
- llms.txt coverage already in sync (no new .mdx files)

Mintlify auto-deploy:
- New .github/workflows/mintlify-deploy.yml — pings the deploy hook on
  every push to main, bypassing the GitHub App's path-detection bug
  that caused docs.mem0.ai drift (the recurring "trigger redeploy"
  commits). Workflow is a clean no-op until MINTLIFY_DEPLOY_HOOK_URL
  repo secret is configured in dashboard.
This commit is contained in:
Mgeeeek
2026-05-20 18:36:57 +05:30
parent 4ca9d13c47
commit 859c674956
9 changed files with 202 additions and 7 deletions
+39
View File
@@ -0,0 +1,39 @@
name: Mintlify Deploy
# Pings the Mintlify deploy hook on every push to main, unconditionally.
#
# Why: the Mintlify GitHub App detects docs changes by path-matching the
# diff, and historically misses some legitimate docs commits — docs.mem0.ai
# drifts out of sync and we have to push a no-op commit to force a redeploy
# (see e.g. 843ab829 "chore: trigger Mintlify redeploy for #5152 docs").
# Calling the hook on every push to main bypasses path detection entirely.
#
# Prerequisite: set repo secret MINTLIFY_DEPLOY_HOOK_URL to the value
# generated in the Mintlify dashboard under Settings → Deploy Hooks.
# If the secret is absent the workflow is a clean no-op (prints a warning
# and exits 0) so this commit is safe to merge before the secret exists.
on:
push:
branches: [main]
workflow_dispatch: {}
permissions:
contents: read
jobs:
trigger:
runs-on: ubuntu-24.04-arm
timeout-minutes: 2
steps:
- name: POST to Mintlify deploy hook
env:
HOOK: ${{ secrets.MINTLIFY_DEPLOY_HOOK_URL }}
run: |
if [ -z "$HOOK" ]; then
echo "::warning::MINTLIFY_DEPLOY_HOOK_URL is not configured; skipping deploy hook ping."
exit 0
fi
curl -sS --fail -X POST "$HOOK" -o /tmp/mintlify.out -w "HTTP %{http_code}\n"
echo "Deploy hook response:"
cat /tmp/mintlify.out