mcpField
F
find-release

find-release

github.com/flutterDevelopment180.5k108 installsUpdated today
Repository

About find-release

A workflow skill for finding which Flutter or Dart release contains a commit, using its SHA and a release channel. It guides running `find_release.dart` and presenting the relevant tags and versions.

Key features

  1. 01Identify commit SHA and channel
  2. 02Run `find_release.dart`
  3. 03Report repository, tag, and release versions
  4. 04Handle missing commits and invalid channels

Use cases

  1. 01Find a commit's stable release
  2. 02Check whether a commit is in beta
  3. 03Look up the release containing a commit

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/flutter/flutter --skill find-release

After installing, type/find-releasein Claude Code to confirm it loaded.

Details

From the project README

Instructions

  1. Extract Information:

    • Identify the commit SHA from the user's request (e.g., 02abc57).
    • Identify the target channel (one of: stable, beta, dev). If not specified, try each.

  2. Execute Search:

    • Ensure the find_release.dart tool is available. The tool is typically located at find_release.dart relative to the Flutter workspace root. If the workspace root is not the default, set the environment variable FIND_RELEASE_TOOL_PATH to the absolute path of the tool.
    • Run the tool using the path to ensure it works from any directory within the workspace.
    • Command: dart run ${FIND_RELEASE_TOOL_PATH:-engine/src/flutter/third_party/dart/tools/find_release.dart} --commit=<SHA> --channel=<CHANNEL>

  3. Interpret and Report Results:

    • The tool will report which repository (dart-lang/sdk or flutter/flutter) the commit was found in.
    • It will provide the "Lowest release tag" (the git tag containing the commit).
    • It will provide the "Lowest Flutter release" and/or "Lowest Dart release" version for the specified channel.
    • Present these findings clearly to the user. If the commit is not found or not yet in a release for that channel, inform the user accordingly.
    • Handle edge cases: If the SHA is invalid or not found, suggest checking the SHA. If the channel is invalid, default to stable and notify the user.

Examples

  • User: "When did commit 02abc57 land in stable?"

  • Agent: Runs dart run ${FIND_RELEASE_TOOL_PATH:-engine/src/flutter/third_party/dart/tools/find_release.dart} --commit=02abc57 --channel=stable and reports the release version.

  • User: "Is 02abc57 in beta?"

  • Agent: Runs the command with --channel=beta.

Comments

Markdown supported