legend-release

Plugin legend-release from marketplace legend in finos/legend-shared. Commands read from the repo's manifest — today.

Skills (7)

• post-release-verify

  Verify a Legend release actually completed — artifacts readable on Central, tag correct, branch left at the right next SNAPSHOT, docker images pushed. Use after a release run goes green, or for "did the release work", "check the release landed", "verify 4.143.1".

• release-backport

  Backport a fix to a Legend release branch safely, without dragging maven-release-plugin commits along with it. Use for "backport this to 4.100", "cherry-pick that fix onto the release branch", "get this fix into the release".

• release-cleanup

  Undo a failed or partial Legend release — inspect what the release actually did, then surgically remove the tag and version-bump commits so the version can be cut again. Use for "the release failed, clean it up", "undo the release commits", "delete the tag so I can re-release", "the version bump was

• release-dispatch

  Dispatch a Legend release workflow and babysit it to completion — picks the right workflow, runs preflight, confirms, triggers, then watches and triages any failure. Use for "release 4.143.1", "cut a release off this branch", "run the release action", "kick off the release".

• release-preflight

  Verify a Legend repo is actually releasable before dispatching a release — tag free, version unpublished on Central, branch clean and pushed, pom version correct, no stray release-plugin commits. Use before any release dispatch, or when asked "can I release X", "is the branch ready", "check before I

• release-train

  Sequence a full Legend stack release across repos — shared, pure, engine, sdlc, depot — in dependency order, bumping each consumer's version properties as the previous one lands on Central. Use for "release the stack", "do the full release train", "release everything for 4.101", "what's next in the

• release-triage

  Diagnose a failed Legend release or CI run — pull the failed jobs, separate real code failures from known environmental/flaky ones, and recommend an action. Use for "why did the release fail", "what broke", "triage this run", or any failed release/build run.