om-auto-upgrade-0.6.7-to-0.7.0

Migrates downstream Open Mercato apps from 0.6.7 to 0.7.0 with bounded edits and audits.

1.7k|382|Updated Sep 10, 2025
One-click install
npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-upgrade-0-6-7-to-0-7-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-auto-upgrade-0.6.7-to-0.7.0
Source: https://github.com/open-mercato/open-mercato/tree/main/packages/create-app/agentic/shared/ai/skills/om-auto-upgrade-0.6.7-to-0.7.0
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-upgrade-0-6-7-to-0-7-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading a downstream Open Mercato application from 0.6.7 to 0.7.0 involves dozens of breaking changes across TanStack Table imports, settings group IDs, removed environment flags, auth, search ACLs, Redis, and webhooks. Doing this by hand is error-prone, and blindly automating it risks corrupting secrets, ACLs, or workflow intent. This Skill applies only the exact, safe mechanical edits automatically and reports everything else as explicit manual findings.

Core Features & Use Cases

  • Twenty-one classified upgrade checks: Each change is classified as automatic-when-exact, detect-and-report, or no-code-action, covering TanStack Table v9, settings section group IDs, module fact sheets, JWT secrets, passkey MFA, search ACLs, ioredis RESP2, webhook body limits, and more.
  • Bounded, idempotent edits: Automatic fixes apply only to exact matches (e.g., repointing a single-specifier ColumnDef import to LegacyColumnDef), preserving formatting and never touching lockfiles, generated output, or secrets.
  • Dry-run planning and verification: --dry-run prints the full plan without edits; after edits, the Skill runs the app's own generate, typecheck, test, and build scripts and reverts any edit that causes a new failure.
  • Use Case: After installing @open-mercato/* 0.7.0 in your downstream CRM app, run the Skill to automatically fix the TanStack import and settings groupId, then receive a report listing the JWT secret cutover, role-ACL sync, and Redis protocol decisions you must handle manually.

Quick Start

Ask the agent to upgrade my Open Mercato app from 0.6.7 to 0.7.0 using a dry run first to review the plan.

Frequently Asked Questions about om-auto-upgrade-0.6.7-to-0.7.0

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

FAQPage Schema
How do I upgrade Open Mercato from 0.6.7 to 0.7.0?

Install the 0.7.0 @open-mercato packages first, then run this upgrade skill against your downstream app. It applies exact safe edits automatically, such as the TanStack ColumnDef import change, and reports all intent-sensitive changes like JWT secret rotation and search ACL grants as manual work.

What code changes does the Open Mercato 0.7.0 upgrade automate?

It automatically rewrites exact single-specifier ColumnDef type imports to LegacyColumnDef, replaces the settings groupId 'module-configs' with 'settings.sections.moduleConfigs', removes the obsolete example-injection env flag line, and repoints flat module fact-sheet paths. Everything else is detected and reported for manual review.

Can I preview the 0.7.0 migration changes before editing files?

Yes, run with the --dry-run flag to detect, classify, and report every match without editing files or running mutating commands. The plan lists each finding with check ID, file, line, classification, and proposed action.

Does the upgrade modify secrets, lockfiles, or framework packages?

No. The skill never changes dependency versions, lockfiles, generated output, vendor files, framework-owned packages, or secrets. It never prints environment variable values and never generates or persists a JWT_SECRET.

What manual work remains after the automated 0.7.0 upgrade?

Manual items include the JWT secret and legacy-token cutover decision, passkey credentials enrolled through the attestation shortcut, role-ACL sync for global and hybrid search, stored workflow template review, Redis RESP2 protocol choice, webhook proxy limits, and design-system and security-header adoption.

What happens if an automatic edit breaks my build?

The skill runs your app's generate, typecheck, test, and build scripts after editing. If an automatic edit causes a new failure, it reverts only that edit and moves the match to manual follow-up, while preserving and reporting any pre-existing failures.