Skip to content

mergetrain 3.0.0

Choose a tag to compare

View all tags
@yongjip yongjip released this 03 Sep 04:22
· 55 commits to main since this release
Immutable release. Only release title and notes can be modified.
v3.0.0
This tag was signed with the committer’s verified signature.
yongjip Yongjip Kim
SSH Key Fingerprint: GzYcD3pog7t8Yikk8XJwwbuRkNdrYvISkNGogPNNCIc
Verified
Learn about vigilant mode.
0dfe090

A smaller, durable product grammar

mergetrain 3.0.0 reduces the everyday product to six lifecycle verbs:

init → status → enqueue → validate → deploy → inspect

The default help, generated agent instructions, Claude plugin, MCP adapter,
quickstart, convenience scripts, and LLM reference files now use that same
grammar. Internal queue states are projected into five operator states:
Waiting, Running, Ready, Attention, and Done.

What changed

  • deploy now owns the full human flow: validate if needed, show one exact
    plan, confirm, recheck, atomically push, and verify.
  • Normal users no longer handle train IDs, SHAs, plan hashes, preview modes,
    or reuse switches.
  • MCP is reduced from twelve tools to five: status, inspect, validate, enqueue,
    and deploy.
  • Starter config contains only the schema version, project name, and gates;
    safe defaults remain built in.
  • Removed v2 commands fail with a typed migration error instead of silently
    behaving differently.

Long-lived compatibility commitment

Contract 3 freezes the six command names, five MCP tool names, config-schema-2
readability, error envelope, and existing JSON meanings. Future 3.x releases
are intended to be additive and there is no planned successor command grammar.

All existing exact-SHA, combined validation, semantic-conflict attribution,
destination and policy binding, atomic-push, and durable-recovery guarantees
remain intact.

See the changelog
for the complete migration details.

Assets 3
Loading