[Upgrade] Shopify Partner - api version upgrade

[jcortes]

WHY

Resolves #18747

Summary by CodeRabbit

• New Features

  • Updated to the 2025-10 Shopify Partner API, enabling access to the latest capabilities and improvements.

• Chores

  • Incremented package and component versions across Shopify Partner actions and sources.
  • Routine metadata updates to ensure compatibility and stability (no functional changes to existing triggers or actions).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs	Ignored			Oct 15, 2025 8:48pm
pipedream-docs-redirect-do-not-edit	Ignored			Oct 15, 2025 8:48pm

[coderabbitai]

Walkthrough

Version strings were updated across multiple Shopify Partner sources and an action. The package version and a dependency were bumped. The Partner GraphQL API version constant was updated from "2024-10" to "2025-10". No functional logic or control-flow changes were introduced in the diffs.

Changes

Cohort / File(s)	Summary
API version constant update components/shopify_partner/shopify_partner.app.mjs	Updated PARTNER_API_VERSION from "2024-10" to "2025-10" for Partner GraphQL endpoint targeting.
Package and dependency bump components/shopify_partner/package.json	Version: 0.1.5 → 0.1.6. Dependency @pipedream/platform: ^1.6.0 → ^3.1.0.
Action version bump components/shopify_partner/actions/verify-webhook/verify-webhook.mjs	Action version: "0.0.7" → "0.0.8". No logic changes.
Source version bumps components/shopify_partner/sources/new-app-charges/new-app-charges.mjs, components/shopify_partner/sources/new-app-installs/new-app-installs.mjs, components/shopify_partner/sources/new-app-relationship-events/new-app-relationship-events.mjs, components/shopify_partner/sources/new-app-uninstalls/new-app-uninstalls.mjs	Source versions updated: charges 0.0.18 → 0.0.19; installs 0.1.3 → 0.1.4; relationship-events 0.1.3 → 0.1.4; uninstalls 0.1.3 → 0.1.4. No logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A rabbit taps deploy with glee,
“New tags, new hops—version spree!”
The Partner path now points ahead,
From 2024 to 2025 we tread.
With whiskers twitching, ears upright,
I nibble bugs and ship the night.

Pre-merge checks and finishing touches

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "[Upgrade] Shopify Partner - api version upgrade" directly addresses the main change in this pull request, which is updating the Shopify Partner API version from "2024-10" to "2025-10" as specified in the linked issue #18747. The title is specific, concise, and clearly indicates the primary objective of the changeset without unnecessary noise or vague terminology.
Linked Issues Check	✅ Passed	The primary requirement from linked issue #18747 is fully met: the PARTNER_API_VERSION constant has been updated from "2024-10" to "2025-10" in the shopify_partner.app.mjs file, which directly resolves the reported issue that requests had stopped working due to the deprecated API version. The changeset includes the core fix requested in the issue along with routine version bumps to affected components, which are consistent with the scope of upgrading a component's API version.
Out of Scope Changes Check	✅ Passed	The primary change (updating PARTNER_API_VERSION to "2025-10") directly addresses the core requirement from issue #18747. Additional changes in the pull request include version bumps to related components (verify-webhook, package.json, new-app-installs, new-app-relationship-events, and new-app-uninstalls), along with a dependency update for @pipedream/platform. These appear to be routine versioning updates and maintenance changes that typically accompany significant API version upgrades to reflect the scope of changes and ensure component compatibility.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-shopify-partner-api-version

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba23007 and 1ba2e61.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (7)

• components/shopify_partner/actions/verify-webhook/verify-webhook.mjs (1 hunks)
• components/shopify_partner/package.json (2 hunks)
• components/shopify_partner/shopify_partner.app.mjs (1 hunks)
• components/shopify_partner/sources/new-app-charges/new-app-charges.mjs (1 hunks)
• components/shopify_partner/sources/new-app-installs/new-app-installs.mjs (1 hunks)
• components/shopify_partner/sources/new-app-relationship-events/new-app-relationship-events.mjs (1 hunks)
• components/shopify_partner/sources/new-app-uninstalls/new-app-uninstalls.mjs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: pnpm publish
• GitHub Check: Verify TypeScript components
• GitHub Check: Publish TypeScript components
• GitHub Check: Lint Code Base

🔇 Additional comments (8)

components/shopify_partner/sources/new-app-charges/new-app-charges.mjs (1)

8-8: LGTM! Version bump aligns with the API upgrade.

The component version increment is appropriate for tracking the Shopify Partner API version upgrade from "2024-10" to "2025-10".

components/shopify_partner/sources/new-app-uninstalls/new-app-uninstalls.mjs (1)

9-9: LGTM! Version bump aligns with the API upgrade.

The component version increment is appropriate for tracking the Shopify Partner API version upgrade from "2024-10" to "2025-10".

components/shopify_partner/package.json (2)

3-3: LGTM! Package version bump is appropriate.

The package version increment from 0.1.5 to 0.1.6 correctly reflects the API version upgrade changes.

---

13-13: Verify @pipedream/platform exports in common/common.mjs
Confirm that ConfigurationError and DEFAULT_POLLING_SOURCE_TIMER_INTERVAL are still exported and behave identically in @pipedream/platform@^3.1.0 before merging.

components/shopify_partner/sources/new-app-relationship-events/new-app-relationship-events.mjs (1)

10-10: LGTM! Version bump aligns with the API upgrade.

The component version increment is appropriate for tracking the Shopify Partner API version upgrade from "2024-10" to "2025-10".

components/shopify_partner/sources/new-app-installs/new-app-installs.mjs (1)

9-9: LGTM! Version bump aligns with the API upgrade.

The component version increment is appropriate for tracking the Shopify Partner API version upgrade from "2024-10" to "2025-10".

components/shopify_partner/actions/verify-webhook/verify-webhook.mjs (1)

6-6: LGTM! Version bump aligns with the API upgrade.

The action version increment is appropriate for tracking the Shopify Partner API version upgrade from "2024-10" to "2025-10".

components/shopify_partner/shopify_partner.app.mjs (1)

4-4: Confirm Partner API version bump and update affected GraphQL usage

• 2025-10 is the correct, latest Partner API version.
• Several breaking changes landed since 2024-10 (e.g., productDuplicate/media/variant mutations, metafield/request format changes, uncapped counts, validation/behavior updates).
• Review each release’s changelog and adjust your GraphQL queries and mutations to match the new schema.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[luancazarine]

Hi @jcortes, LGTM! Ready for QA!