What problem does it solve?
Testing an unreleased Metro compiler or Gradle plugin change against a real consumer project is error-prone: stale artifacts, wrong repository ordering, and cached outputs can hide whether the fix actually works. This Skill provides a disciplined workflow for publishing a uniquely-versioned Metro build to Maven Local and verifying it downstream.
Core Features & Use Cases
- Unique local publishing: Derives a task-specific version from
VERSION_NAME and publishes via ./metrow publish --local, avoiding partial or reused artifacts.
- Consumer configuration: Adds
mavenLocal() to plugin and dependency repositories and points the consumer at the unique version without disturbing unrelated build settings.
- Verified resolution: Confirms via
buildEnvironment and dependencyInsight that the exact local version was selected, and reports baseline versus local outcomes per Metro mode.
- Use Case: A contributor fixes a Metro FIR code generation bug reported in a GitHub issue, publishes
1.4.0-2587-20260725-LOCAL01 to Maven Local, and reruns the reporter's failing Gradle task to confirm the fix.
Quick Start
Ask the assistant to publish this Metro checkout to Maven Local and verify the change in your downstream reproducer project.