Allow theme commands to use glob patterns for the --environment flag

[graygilmore]

WHY are these changes introduced?

• Fixes [Feature] Support glob patterns in theme environment flags #6481

Some theme commands accept multiple environments to be specified but it can be annoying to write them all out if you have many environments that follow a certain pattern.

This PR allows you to specify environment names using glob patterns:

shopify theme push -e "*-production"

The above example will try to match all environments defined in your shopify.theme.toml file that end with -production. We're support all pattern matching from minimatch including these common patterns:

• *: Matches zero or more characters
• ?: Matches exactly one character
• []: Matches any single character within the brackets
• {}: Matches any of the comma-separated patterns

How to test your changes?

Install the snapped version:

npm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20251008192534

Try running commands with glob patterns:

shopify theme info -e "test*"

With a shopify.theme.toml that looks like this:

[environments.test1]
store = "test1"
password = "asdf"

[environments.test2]
store = "test2"
password = "asdf"

[environments.test3]
store = "test3"
password = "asdf"

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	79.05% (+0.07% 🔼)	13381/16928
🟡	Branches	72.75% (+0.09% 🔼)	6536/8984
🟡	Functions	79.24% (+0.05% 🔼)	3455/4360
🟡	Lines	79.41% (+0.07% 🔼)	12639/15917

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / fs.ts	87.83% (-0.41% 🔻)	92.31% (-2.69% 🔻)	85.42% (+0.63% 🔼)	88.29% (+0.29% 🔼)

Test suite run success

3265 tests passing in 1347 suites.

Report generated by 🧪jest coverage report action from e4bb2d9

[graygilmore]

Instead of matching against this we could always parse with minimatch but this would result in us ignoring the flag if it doesn't find any matches.

While this is open for review I'm going to play around with the consequences of that approach.

[graygilmore]

/snapit

[github-actions]

🫰✨ Thanks @graygilmore! Your snapshot has been published to npm.

Test the snapshot by installing your package globally:

npm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20251008192534

Caution

After installing, validate the version by running just shopify in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.

[graygilmore]

/snapit

[github-actions]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/node/environments.d.ts

@@ -8,9 +8,26 @@ interface LoadEnvironmentOptions {
 }
 /**
  * Loads environments from a file.
- * @param dir - The file path to load environments from.
- * @returns The loaded environments.
+ * @param environmentName - The name of the environment.
+ * @param fileName - The file name to load environments from.
+ * @param options - Optional configuration for loading.
+ * @returns The loaded environment.
  */
 export declare function loadEnvironment(environmentName: string, fileName: string, options?: LoadEnvironmentOptions): Promise<JsonMap | undefined>;
 export declare function environmentFilePath(fileName: string, options?: LoadEnvironmentOptions): Promise<string | undefined>;
+/**
+ * Gets all available environment names from a file.
+ * @param fileName - The file name to load environments from.
+ * @param options - Optional configuration for loading.
+ * @returns Array of environment names, or empty array if none found.
+ */
+export declare function getEnvironmentNames(fileName: string, options?: LoadEnvironmentOptions): Promise<string[]>;
+/**
+ * Expands environment patterns (including globs) to actual environment names.
+ * @param patterns - Array of environment names or glob patterns.
+ * @param fileName - The file name to load environments from.
+ * @param options - Optional configuration for loading.
+ * @returns Array of matched environment names.
+ */
+export declare function expandEnvironmentPatterns(patterns: string[], fileName: string, options?: LoadEnvironmentOptions): Promise<string[]>;
 export {};
\ No newline at end of file

[github-actions]

🫰✨ Thanks @graygilmore! Your snapshot has been published to npm.

Test the snapshot by installing your package globally:

npm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20251009161632

Caution

After installing, validate the version by running just shopify in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.