GitHub Actions / GitHub Actions

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

Fix ESM action crashes after @actions/glob v0.7.0 upgrade — broken import of Minimatch named export Includes evidence for GitHub Actions troubleshooting demand.

Source-backed Last updated May 17, 2026 1 source Needs local verification

Category: GitHub Actions
Error signature: SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0)
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 17, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

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

Confirm the exact error signature matches SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0).
Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
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

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
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.

Diagnostic flow for this page

Match SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0) exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0) mean in GitHub Actions?

SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0) indicates the workflow described by "@actions/glob v0.7.0 breaks ESM actions — Minimatch not a named export in minimatch v10" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0)?

Check whether this cause matches your environment: 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.

Is the SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0) guidance source-backed?

The "@actions/glob v0.7.0 breaks ESM actions — Minimatch not a named export in minimatch v10" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0)?

For "@actions/glob v0.7.0 breaks ESM actions — Minimatch not a named export in minimatch v10", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging SyntaxError: The requested module 'minimatch' does not provide an export named 'Minimatch' (in @actions/glob v0.7.0)?

For "@actions/glob v0.7.0 breaks ESM actions — Minimatch not a named export in minimatch v10", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.