chore(deps): update dependency @shopify/api-codegen-preset to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@shopify/api-codegen-preset (source)	^1.1.1 → ^2.0.0

---

Release Notes

Shopify/shopify-app-js (@​shopify/api-codegen-preset)

v2.0.1

Patch Changes

• e510582: Updated @graphql-codegen/introspection, @​graphql-codegen/typescript, isbot dependencies

• 57b5f18: Updated @graphql-codegen/cli dependencies

• 9debf0d: Updated graphql dependencies

• f86b725: Updated graphql, mysql2, pg, mongodb, pg-connection-string, redis dependencies

• c8a8355: Fix custom GraphQL scalars generating as any in codegen output

  Shopify API custom scalars (e.g. DateTime, Money, URL, HTML) now
  correctly generate as string in codegen output instead of any. The JSON
  scalar generates as unknown. This applies automatically to all current and
  future Shopify API scalars without requiring manual configuration.

  Fixes #​1154

v2.0.0

Major Changes

• 050114d: Updated @graphql-codegen/introspection from v4 to v5. Dropped Node 18 support.
• 0b27130: Updated @graphql-codegen/cli from v5 to v6

Patch Changes

• af723c8: Updated graphql dependencies
• 4c1789b: Updated @graphql-codegen/typescript, @​parcel/watcher, isbot dependencies
• 822e244: Fixed TypeScript compilation error (ts5097) for users without allowImportingTsExtensions by using .js extensions for generated import paths. The .js extension works across all TypeScript module resolution strategies.
• d5ae946: Publish TypeScript source files to npm so "Go to Definition" in IDEs navigates to real source code instead of compiled .d.ts declaration files. Source maps already pointed to the correct paths — the source files just weren't included in the published packages.

v1.2.2

Patch Changes

• b69d09f: bump @​graphql-codegen/typescript from 4.1.6 to 5.0.1

v1.2.1

Patch Changes

• 62394e5: Fixed TypeScript module resolution error by including file extensions (.d.ts or .ts) in generated import paths to support Node16/NodeNext module resolution strategies.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "on monday before 8am"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: examples/shopify-integration/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "auto-install-peers". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "shamefully-hoist". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown project config "enable-pre-post-scripts". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: javascript-integration@undefined
npm error Found: react@19.2.7
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error   peer react@"*" from @shopify/shopify-app-remix@4.2.1
npm error   node_modules/@shopify/shopify-app-remix
npm error     @shopify/shopify-app-remix@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @remix-run/react@2.17.5
npm error node_modules/@remix-run/react
npm error   @remix-run/react@"^2.7.1" from the root project
npm error   peer @remix-run/react@"*" from @shopify/shopify-app-remix@4.2.1
npm error   node_modules/@shopify/shopify-app-remix
npm error     @shopify/shopify-app-remix@"^4.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-07-12T10_10_37_232Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-12T10_10_37_232Z-debug-0.log