convex-check-updates

Detects stale Convex components and upgrades them behind a build gate.

9.4k|1.5k|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/openclaw/clawhub --skill convex-check-updates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-check-updates
Source: https://github.com/openclaw/clawhub/tree/main/.agents/skills/convex-check-updates
Command: npx skills add https://github.com/openclaw/clawhub --skill convex-check-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convex apps pin component versions that drift out of date over time, and upgrading them blindly risks breaking the build or leaving the app half-migrated. This Skill checks pinned components against the registry and upgrades them one at a time with verification gates.

Core Features & Use Cases

  • Stale Component Detection: Runs a check script against the anteater registry to list each outdated component with installed vs. current versions, summaries, and breaking-change flags.
  • Gated Upgrades: Applies each upgrade individually, running migration steps and gate commands (typecheck + build) before moving to the next component.
  • Safe Rollback: Reverts via git checkout or reinstalling the old ref if any gate fails, and requires a snapshot before breaking upgrades.
  • Use Case: Before a release, ask the agent to check your Convex app's components; it reports three stale packages, then upgrades each one behind a build gate with your explicit approval.

Quick Start

Ask the agent to check my Convex app's pinned components for updates and upgrade any stale ones with my approval.

Frequently Asked Questions about convex-check-updates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for outdated Convex components in my app?

Run the check-updates script from the project root, which compares pinned components against the anteater registry. It reports each stale entry with installed and current versions, a summary, and a breaking-change flag.

How to safely upgrade Convex components without breaking the build?

Upgrade one component at a time behind a build gate that runs typecheck and build commands after each migration step. If any gate command fails, revert with git checkout or by reinstalling the old ref before continuing.

Does the upgrade happen automatically without confirmation?

No. The workflow requires an explicit user yes before any upgrade, even for minor versions. Breaking upgrades additionally require a snapshot such as a commit or branch before changes are applied.

What happens if a Convex component migration fails midway?

The process reverts the changes using git checkout or by reinstalling the old component ref, then reports the failure. It never leaves the app half-migrated and does not proceed to the next component.

Will my live convex.app site be republished after an upgrade?

Not automatically. The rules explicitly prohibit republishing a live *.convex.app site after upgrading without separate user confirmation, keeping production deployments under manual control.