@actions/glob v0.7.0 breaks ESM actions — Minimatch not a named export in minimatch v10

What this error means

SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0) is a GitHub Actions failure pattern reported for developers trying to fix esm action crashes after @actions/glob v0.7.0 upgrade — broken import of minimatch named export. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Found in actions/toolkit issue #2408 (2026-05-15). Bumping minimatch from v3 to v10 broke named export compatibility. Any GitHub Action using @actions/glob in ESM context will crash at runtime. CI/CD impact for teams using pinned actions. Category: GitHub Actions.

Common causes

• Found in actions/toolkit issue #2408 (2026-05-15). Bumping minimatch from v3 to v10 broke named export compatibility. Any GitHub Action using @actions/glob in ESM context will crash at runtime. CI/CD impact for teams using pinned actions. Category: GitHub Actions.

Quick fixes

1. Confirm the exact error signature matches SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0).
2. Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/actions/toolkit/issues/2408

Evidence note: Found in actions/toolkit issue #2408 (2026-05-15). Bumping minimatch from v3 to v10 broke named export compatibility. Any GitHub Action using @actions/glob in ESM context will crash at runtime. CI/CD impact for teams using pinned actions. Category: GitHub Actions.

Related errors

• GitHub Actions

FAQ

What should I check first?

Start with the exact SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0) text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed GitHub Actions workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0).