Error "labels is invalid" deploying to Oxygen

Hi im encountering this error that I have no idea where it comes from when deploying hydrogen to oxygen through github:

I tried to create two different shops and deploy it succesfully for first time, but after just some styling changes and a push to main this “labels is invalid” error happens always to me, and the checks are not passed.

My local environment with mini-oxygen is working perfectly and I can also run npm run build with no errors.

Does anyone know what this error is? I dont know which other information would be helpfull in this case to show to you. So if anyone needs more please let me know. I would appreciate your help, thanks !

4 Likes

Exact same happening to me. I deployed successfuly 26 mins ago. Now, I can’t deploy anything. No changes were made to my set up.

1 Like

I’ve been all day long talking with support about this and also because I couldnt even create a new project with the command npm create @Shopify_77 [email removed] and choosing connect with an existing shop, either conect a github repo with new shopify storefront.

I have a feeling about there is something to fix about the last release of the hydrogen library, but actually no idea. If I know something from them again I will come back to here.

2 Likes

Same happening here.

Started failing yesterday (10/28/23) afternoon… deployed successfully from github repo at 1:21pm PDT.

No changes in setup. Just, code changes. Everything runs fine locally. Local production build is fine.

On next github repo commit/push at 10/28/23 5:21pm PDT, deployment to Oxygen failed. Continues to fail with same message:

158 Failed to create build. Labels is invalid
159 › Error: EEXIT: 1

160 › Code: EEXIT

161 Error: Process completed with exit code 1.

1 Like

Same problem here.
Did manage to deploy successfully after triggering a manual re-run trough Github.

Can confirm same for me. For my production branch, I re-ran the workflow in Git and it deployed successfully. Not the case for my staging branch, as still getting errors on that one.