om-auto-upgrade-0.6.6-to-0.6.7

Migrates downstream Open Mercato apps from version 0.6.6 to 0.6.7 with bounded edits.

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-6-to-0-6-7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-auto-upgrade-0.6.6-to-0.6.7
Source: https://github.com/open-mercato/open-mercato/tree/main/packages/create-app/agentic/shared/ai/skills/om-auto-upgrade-0.6.6-to-0.6.7
Command: npx skills add https://github.com/open-mercato/open-mercato --skill om-auto-upgrade-0-6-6-to-0-6-7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading a downstream Open Mercato application from 0.6.6 to 0.6.7 involves breaking changes like moved pg-errors imports, flattened scheduler queue payloads, and removed scheduler metadata that are tedious and error-prone to fix by hand.

Core Features & Use Cases

  • Automatic import migration: Rewrites the exact @open-mercato/core/modules/communication_channels/lib/pg-errors module specifier to @open-mercato/shared/lib/db/pg-errors while preserving imported names and formatting.
  • Proven scheduler payload unwrapping: Removes the redundant .payload segment from <job>.payload.payload.<field> accesses only after proving the consumer handles a queue targeted by a scheduler registration in the same repository.
  • Detect-and-report audits: Flags scheduler consumers reading removed metadata (scheduleId, scheduleName, scopeType, triggeredAt) and query-index callbacks that swallow encryption errors, without inventing replacements.
  • Use Case: After installing Open Mercato 0.6.7 in your downstream app, run this Skill with --dry-run to preview every required change, then apply the bounded edits and verify with typecheck, tests, and build.

Quick Start

Ask the AI to upgrade your Open Mercato app from 0.6.6 to 0.6.7 using this skill, optionally with a dry run first to review the plan.

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

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

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

Install version 0.6.7 in your downstream app, then run this upgrade skill to apply the mechanical changes. It rewrites the pg-errors import, unwraps proven scheduler payload accesses, and reports manual follow-ups before running typecheck, tests, and build.

How do I preview the 0.6.7 upgrade changes before editing code?

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

Can I run the upgrade on only specific checks?

Yes, use --only with comma-separated check IDs to limit work, or --skip to omit named checks. The two flags cannot be combined, and skipped checks are recorded in the final report.

Does the upgrade skill modify the Open Mercato framework monorepo?

No, it refuses to run when the target contains the framework monorepo's packages/core and packages/shared workspaces. It also never edits dependency pins, lockfiles, generated output, or vendored directories.

Why does the skill not auto-fix removed scheduler metadata?

Fields like scheduleId, scheduleName, scopeType, and triggeredAt were removed from scheduler job payloads in 0.6.7. The skill only reports these usages and tells you to include required values explicitly in targetPayload, since it never invents replacement values.

What happens if typecheck or tests fail after an upgrade edit?

The skill stops at the first new failure caused by an edit, reverts only that edit, and moves it to manual follow-up. Pre-existing failures are preserved and reported rather than rewritten or hidden.