Back to Details

convex-check-updates

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- GENERATED from convex-agents content/capabilities/check-updates.json — do not edit by hand. -->
<!-- 由 convex-agents content/capabilities/check-updates.json 生成 — 请勿手动编辑。 -->

check-updates

check-updates

Detect stale Convex components in the current app against the anteater registry and, with explicit user consent, upgrade them one at a time behind a build gate (typecheck + next build). Each upgrade is gated and smoke-tested before the next.
检测当前应用中过时的Convex组件（与anteater注册表对比），并在获得用户明确同意后，逐个在构建校验环节（类型检查 + next build）后对其进行升级。每次升级都会经过校验和冒烟测试，之后才会进行下一次升级。

Workflow

工作流程

  1. Run 
    curl -fsSL https://graceful-tiger-715.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjs
    from the project root.
  2. If COMPONENTS_UP_TO_DATE: tell the user; done.
  3. If COMPONENTS_STALE=<n>: list each stale entry (component name, installed → current, summary, breaking flag) and ask the user before touching anything.
  4. On yes: install the new ref, apply each migration.steps change (delegate convex/ edits to convex-expert), run every migration.gate command.
  5. If any gate command fails: revert (git checkout -- . or reinstall old ref) and report; never leave the app half-migrated.
  6. Give the user the smoke check (migration.smoke) to run after each successful upgrade.
  7. Repeat for each stale component, one at a time.
  1. 从项目根目录运行 
    curl -fsSL https://graceful-tiger-715.convex.site/check-updates.mjs -o /tmp/cu.mjs && node /tmp/cu.mjs
    。
  2. 如果组件已更新至最新版本（COMPONENTS_UP_TO_DATE）：告知用户；流程结束。
  3. 如果存在<n>个过时组件（COMPONENTS_STALE=<n>）：列出每个过时条目（组件名称、已安装版本 → 当前版本、更新摘要、是否存在破坏性变更标记），并在进行任何操作前询问用户。
  4. 用户同意后：安装新的引用，应用每个migration.steps中的变更（将convex/目录下的编辑操作委托给convex-expert），运行每个migration.gate命令。
  5. 如果任何校验命令失败：回滚（执行git checkout -- . 或重新安装旧版本引用）并报告；绝不允许应用处于半迁移状态。
  6. 每次成功升级后，告知用户运行冒烟测试（migration.smoke）。
  7. 对每个过时组件重复上述步骤，逐个处理。

Rules

规则

  • Never upgrade without an explicit user yes — not even a minor version.
  • Gate each component individually before moving to the next.
  • breaking:true upgrades require a snapshot (commit or branch) before applying.
  • Do not auto-republish a live *.convex.app site after upgrading without user confirmation.
  • 未经用户明确同意，绝不进行升级——即使是小版本更新也不行。
  • 在处理下一个组件前，单独对每个组件进行校验。
  • 标记为breaking:true的升级需要先创建快照（提交或分支），然后再应用。
  • 升级后未经用户确认，不得自动重新发布已上线的*.convex.app站点。