Skip to content
Skills Library
DevOps & cloud · Automation

release-dispatch

/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".

Author
finos ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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".

Triggers from the description

release 4.143.1cut a release off this branchrun the release actionkick off the release
Original author description

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".

How it works

  1. 1. Establish the target
  2. 2. Preflight
  3. 3. Confirm before dispatching
  4. 4. Dispatch
  5. 5. Babysit
  6. 6. On failure
  7. 7. On success
Original SKILL.md headings · 80 lines, 468 words
SKILL.md preview
---
name: release-dispatch
description: 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 dispatch

Dispatches a release and stays with it. The point is that the user does not have
to watch a 1–3 hour pipeline or discover a failure an hour after it happened.

Read `../release-preflight/references/repo-matrix.md` (relative to this skill's directory) before anything.

## 1. Establish the target

Repo from `git remote get-url origin`, branch and version from the user. If they
gave a version but no branch, use the current branch and say which one you are using.

**Pick the workflow from the matrix, not from the file listing.** `release.yml`
is correct for all five repos. Do not use `release-large-runner.yml` (dead since
February 2026) or `legend-stack-release.yml` (stale, `repository_dispatch`-driven).

Verify with actual history rather than assumption:
```bash
gh run list --workflow=release.yml -L 5
```

## 2. Preflight

Run the `release-preflight` skill's checks in full. If anything blocks, stop and
report — do not dispatch "to see what happens", because a failed release after
`release:prepare` leaves a pushed tag and version commits to clean up.

## 3. Confirm before dispatching

Dispatching publishes to Maven Central, which is **immutable**. Always confirm,
stating plainly:

- repo, branch, version, workflow
- whether it is a real publish or a dry run
- the expected duration from recent runs of that workflow

**The dry-run trap** (`legend-pure` and `legend-engine` only): `dryRun: true`
skips only the *publish* steps. `release:prepare` still runs, so it still pushes
the tag and the version-bump commits. A dry run followed by a real run therefore
needs a full `release-cleanup` in between. Say this whenever the user asks for a
dry run — most people expect it to be side-effect free, and it is not.

## 4. Dispatch

```bash
gh workflow run release.yml --ref <branch> -f releaseVersion=<version>
```
Add `-f dryRun=true` only where the input exists and the user asked for it.
`gh workflow run` prints nothing on success, so confirm it actually started:
```bash
gh run list --workflow=release.yml -L 3
```
Report the run ID and URL.

## 5. Babysit

Poll rather than blocking on `gh run watch`, which holds the terminal for hours:
```bash
gh run view <run-id>
```
Sensible cadence is every few minutes early on, then spaced out — the build job
alone is over an hour on legend-engine. For a long unattended watch, the `loop`
skill fits well.

Report meaningful transitions only: the build job finishing (this is the point
the tag has been pushed and the branch bumped), the test matrix starting, the
publish job starting. Do not narrate every poll.

## 6. On failure

Hand straight to `release-triage`. Do not guess at a cause from the job name —
a single failed job routinely mixes a real failure with an environmental one.
Report the verdict and the recommended action; do not rerun or "fix" anything
without asking.

## 7. On success

Hand to `post-release-verify`.

Versions

The database has no other skills named release-dispatch.

Database snapshot: 13.11.2026 · package version 0428907bc789 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100release-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.
  • 100release-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",…
  • 100release
    Autonomously cut a Rove (`@sma1lboy/rove`) release end-to-end — detect the semver bump from pending changesets (flagging an upstream `minor` you didn't intend), run the release gates, dispatch the Changesets workflow (or run `scripts/release.sh` locally), then poll the GitHub…
  • 100cut-release
    Cut a new agnostic-ai release end to end. Use when the user wants to ship a new version (tag + GitHub Release).
  • 100ci-troubleshoot
    Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read `gh run` logs and retrigger jobs. Use when a CI run is red, a release is stuck, a workflow won''t…
  • 100cut-new-release-candidate
    Use when the user asks to cut, trigger, or start a release candidate for a release branch. Not for full releases, hotfixes, or non-release-candidate workflow dispatches.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.