[Bug]: Shopify CLI - templates/product.json not updated after shopify theme push

[ersanjay5991]

Please confirm that you have:

• [x] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
• [x] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?

Theme

Expected behavior

Changes made to templates/product.json should be detected and pushed without needing extra manual steps.

Actual behavior

When updating the templates/product.json file in a Shopify theme project and using shopify theme push, the CLI does not detect changes or update the file on the store.

Verbose output

Verbose output

Paste the output here!

Reproduction steps

To Reproduce

Steps to reproduce the behavior:

1. Edit templates/product.json locally.
2. Save the file.
3. Run shopify theme push (or shopify theme push templates/product.json).
4. Observe that the file is not updated remotely, and CLI shows "no changes detected."

Operating System

Windows 11

Shopify CLI version (shopify --version)

3.72.2

Shell

powershell

Node version (run node -v if you're not sure)

v22.11.0

What language and version are you using in your application?

No response

[charlespwd]

Can you run the command again with verbose logs? Seems like you might have a .shopifyignore problem?

[ersanjay5991]

Hi @charlespwd

I'm working with a Shopify theme and noticed that there is no .shopifyignore file present in my theme directory. Could you please share the command to create or regenerate this file?

Thanks in advance for your help!

[graygilmore]

He was suggesting that you might have a .shopifyignore file in your directory that is causing the CLI to not upload the file. If you don't have that file then that's not the problem and you don't need to create one. You can learn more about the .shopifyignore file in our docs.

For the original problem: I was not able to replicate the bug as described. If you're still running into this on the latest version of the CLI please re-open the issue with a --verbose log of the command's output. Thanks!