Download, cache, install, and configure the MinIO client (mc) in GitHub Actions.
Optimized for Ubuntu runners and CI use-cases where you want fast, reliable MinIO access without re-downloading on every run.

• ⚡ Weekly cache rotation (no manual version bumps)
• 🔐 Alias configuration with your endpoint & credentials
• 🪣 Optional bucket creation (--ignore-existing)
• 🧪 Optional checksum verification (enabled by default)
• 🛣️ Adds mc to PATH for subsequent steps
• 🧰 Outputs mc-path and mc-version

To use this action in your GitHub workflow, reference it with a specific version tag:

uses: buckhamduffy/gha-minio-cli@v1

For the latest features, you can also use:

• @main - Latest development version (not recommended for production)
• @v1.0.0 - Specific release version

- name: Setup MinIO Client
  uses: buckhamduffy/gha-minio-cli@v1
  with:
    alias: minio
    url: http://localhost:9000
    access_key: ${{ secrets.MINIO_ACCESS_KEY }}
    secret_key: ${{ secrets.MINIO_SECRET_KEY }}

- name: Setup MinIO Client (specific version)
  uses: buckhamduffy/gha-minio-cli@v1
  with:
    alias: minio
    url: http://localhost:9000
    access_key: ${{ secrets.MINIO_ACCESS_KEY }}
    secret_key: ${{ secrets.MINIO_SECRET_KEY }}
    version: 2023-08-23T10-07-06Z

- name: Setup MinIO Client and bucket
  uses: buckhamduffy/gha-minio-cli@v1
  with:
    alias: minio
    url: http://localhost:9000
    access_key: ${{ secrets.MINIO_ACCESS_KEY }}
    secret_key: ${{ secrets.MINIO_SECRET_KEY }}
    bucket: my-bucket

• By default, the action installs the latest MinIO client.
• To install a specific version, set the version input to the desired release string (e.g. 2023-08-23T10-07-06Z).
• The action constructs the download URL as:
  • Latest: https://dl.min.io/client/mc/release/linux-amd64/mc
  • Specific: https://dl.min.io/client/mc/release/linux-amd64/mc.RELEASE.{version}

You can override the download URL entirely with download_url if you need a custom or pre-release binary.

After setup, you can use mc in subsequent steps:

- name: List buckets
  run: mc ls minio

This action follows semantic versioning. To create a new release:

1. Update the version in any relevant files
2. Create a git tag: git tag v1.0.0
3. Push the tag: git push origin v1.0.0
4. Create a GitHub release from the tag
5. Update the major version tag: git tag -f v1 && git push origin v1 --force

This allows users to reference @v1 for the latest v1.x.x release.

To test this action locally:

1. Use the test workflow in .github/workflows/test.yml
2. The workflow sets up a MinIO service and tests various scenarios
3. You can also test against your own MinIO instance by setting the appropriate secrets

MIT

• 🏷️ Version selection: Install a specific MinIO client version or always get the latest (default)