@shopify/oxygen-cli: 4.4.9 ← package making the failing fetch
@shopify/hydrogen: 2024.10.1
Deploy command: npx shopify hydrogen deploy
Auth: SHOPIFY_HYDROGEN_DEPLOYMENT_TOKEN (deployment token, resolves correctly in logs)
What we have already ruled out
Auth/token — token resolves to *** and the deploy step starts; not an auth error.
GitHub Actions cache — purging the node-modules / npm caches did not change the result.
Node version — confirmed running on Node 24 (the current runner default); error is unchanged.
Our application code / the merged PR — a build problem would fail at build; this fails on the Oxygen API fetch and reproduces regardless of content.
A client-side upgrade within our current line — the entire @shopify/cli-hydrogen 8.x line (through 8.4.6) depends on @shopify/oxygen-cli@4.4.9, so there is no patch-level bump available to us without a Hydrogen 2024.10 → 2025.x framework migration.
Our questions
Is there a known Oxygen deploy-API incident or a recent change to oxygen.shopifyapps.com/api/v2/admin/graphql that is incompatible with oxygen-cli@4.4.9?
Is oxygen-cli@4.4.9 (Hydrogen 2024.10) still supported for deploys, or is a CLI/framework upgrade now required? If required, what is the minimum supported version for deploys?
If this is a server-side regression, can it be rolled back / hotfixed while we plan an upgrade?
running shopify hydrogen deploy locally is also inconsistent. it’s had about a 1 in 3 success rate for us. also noticed the same error message when trying to pull environment variables. similar rate of error
Hello again everyone. We’ve confirmed that there have been no platform changes on Shopify’s side. This appears to be caused by a Node security update that landed on LTS in 24.17.0.
Some options:
Downgrade Node to 24.16.0
Ensure @shopify/cli is on a version >= 3.78.0
We recommend bumping @shopify/cli if that’s a reasonable path for you.