bluefireteam/Melos action
Setup Melos for you GitHub workflow
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 22, 2026
- License
- MIT
Pinned Snippet
uses: bluefireteam/melos-action@2982f8e4fc92440a219490009d6d05195cb1a6a5 # v3.8.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| melos-version | The Melos version to make available on the path | no | — |
| dart-version | The dart version to pass to dart-lang/setup-dart action used for publishing, this helps to avoid race condition when having flutter SDK setup with the version different from the latest dart. If 'none' is passed in, the action doesn't set up the dart version at all. | no | stable |
| run-bootstrap | Whether bootstrap should run or not (default: true) | no | true |
| bootstrap-no-example | Whether to pass the --no-example flag to melos bootstrap, this helps to avoid race conditions in flutter packages, where pub get can be executed on the example project before melos has had a chance to generate its pubspec_overrides.yaml (default: false) | no | false |
| enforce-lockfile | Whether the versions in the lockfiles should be enforced (default: false) | no | false |
| run-versioning | Whether packages should be versioned (default: false) | no | false |
| run-versioning-prerelease | Whether packages should be versioned as a prerelease (default: false) | no | false |
| run-versioning-graduate | Whether packages should be versioned with graduating prereleases to stable (default: false) | no | false |
| include-private | Whether to include or exclude packages with `publish_to: "none"` (default: false) | no | false |
| publish-dry-run | Whether packages should be dry-run published (default: false) | no | false |
| tag | Whether packages should be tagged and pushed to the repository (default: false) | no | false |
| publish | Whether packages should be published to pub.dev (default: false) | no | false |
| create-release | Whether a GitHub release should be created for the package related to the tag that triggered the workflow. The release notes are extracted from the package's CHANGELOG.md for the released version (default: false) | no | false |
| release-prerelease | Whether the created GitHub release should be marked as a prerelease. By default this is detected automatically from the version (any version containing a `-`, e.g. `1.2.3-dev.1`, is treated as a prerelease) | no | auto |
| create-pr | Whether a PR should be created with the versioning changes (default: false) | no | false |
| pr-title | The title to use for the PR created when `create-pr` is true (default: "chore(release): Publish packages") | no | chore(release): Publish packages |
| pr-body | The body to use for the PR created when `create-pr` is true (default: "Prepared all packages to be released to pub.dev") | no | Prepared all packages to be released to pub.dev |
| token | Token to use when creating the PR. Use a PAT or GitHub App token to trigger workflows on the created PR (default: GITHUB_TOKEN) | no | ${{ github.token }} |
| git-email | The email to use when committing changes | no | github-actions[bot]@users.noreply.github.com |
| git-name | The name to use when committing changes | no | github-actions[bot] |
Outputs
no outputs