BugError added for unexpected response from BulkOps API

[ericlee878]

Resolves: https://github.com/orgs/shop/projects/208/views/34?pane=issue&itemId=139446745&issue=shop%7Cissues-api-foundations%7C1113

Inspiration from: https://app.graphite.com/github/pr/Shopify/cli/6588/Initial-Setup-Bulk-Operations-Infrastructure-for-Shopify-CLI#comment-PRRC_kwDOHibhHs6WnG-H

Background
When the CLI calls the BulkOps API, the API returns a bulkOperationResponse with two parts: bulkOperation and userErrors. When the code gets the bulkOperationResponse back, the code looks to see if userErrors exist before even looking at the bulkOperation part.

I wanted to deal with the case where the bulkOperation value was null. However, if the bulkOperation value is null, there should be something in userErrors, and the code should have returned the error already (since it checks userErrors before bulkOperation). So, this case should never happen (this case being where bulkOperation is null and userErrors is empty).

I still wanted to write a case for this. So, I wrote BugError that alerts the team if this case ever happens. A BugError is something like Sentry in Core.

Testing
Added unit test to test this code path

[ericlee878]

• BugError added for unexpected response from BulkOps API #6666 👈 (View in Graphite)
• Add stdin support for shopify app execute #6663
• Use ensureAuthenticatedAdminAsApp in shopify app execute #6643 : 1 other dependent PR (#6667 )
• Add --variable-file flag for bulk operation mutations #6636
• Add GraphQL Operation Validation for Bulk Operations CLI #6632
• Add erroring for when variables are given for a BulkOps query #6622
• Implement mutation support for BulkOps CLI command #6596
• Initial Setup: Bulk Operations Infrastructure for Shopify CLI  #6588 : 1 other dependent PR (#6595 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	79.22% (+0% 🔼)	13793/17410
🟡	Branches	73.15% (+0.01% 🔼)	6733/9205
🟡	Functions	79.32%	3541/4464
🟡	Lines	79.6% (+0% 🔼)	13034/16375

Test suite run success

3435 tests passing in 1393 suites.

Report generated by 🧪jest coverage report action from 388de23

[ericlee878]

Not exactly sure if BugError is the right way to throw alerts here. @nickwesselman Is there a way CLI convention for this?

[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/system.d.ts

@@ -62,4 +62,23 @@ export declare function isCI(): boolean;
  *
  * @returns True if the current environment is a WSL environment.
  */
-export declare function isWsl(): Promise<boolean>;
\ No newline at end of file
+export declare function isWsl(): Promise<boolean>;
+/**
+ * Check if stdin has piped data available.
+ * This distinguishes between actual piped input (e.g., )
+ * and non-TTY environments without input (e.g., CI).
+ *
+ * @returns True if stdin is receiving piped data or file redirect, false otherwise.
+ */
+export declare function isStdinPiped(): boolean;
+/**
+ * Reads all data from stdin and returns it as a string.
+ * This is useful for commands that accept input via piping.
+ *
+ * @example
+ * // Usage: echo "your query" | shopify app execute
+ * const query = await readStdin()
+ *
+ * @returns A promise that resolves with the stdin content, or undefined if stdin is a TTY.
+ */
+export declare function readStdinString(): Promise<string | undefined>;
\ No newline at end of file