Skip to content

An fix cookbook recipes 2025 10#3457

Open
andguy95 wants to merge 27 commits intomainfrom
an-fix-cookbook-recipes-2025-10
Open

An fix cookbook recipes 2025 10#3457
andguy95 wants to merge 27 commits intomainfrom
an-fix-cookbook-recipes-2025-10

Conversation

@andguy95
Copy link
Collaborator

@andguy95 andguy95 commented Feb 10, 2026

WHY are these changes introduced?

Closes https://github.com/Shopify/developer-tools-team/issues/986.
Closes https://github.com/Shopify/developer-tools-team/issues/1008.

The cookbook recipes were failing because patches were using an old snapshot of the skeleton template, so when the recipe is applied, it fails.

WHAT is this pull request doing?

  • Fixes the following cookbook recipes by fixing recipes with latest skeleton changes, then regenerate the recipes.
    • b2b
    • bundles
    • combined-listings
    • custom-cart-method
    • express (Skipping for now due to complexity)
    • markets (WIP)
    • metaobjects
    • multipass
    • partytown
    • subscriptions
  • Adds in a /recipe-apply-and-fix.prompt.md Claude command to help aid with fixing recipes by fixing recipes with latest skeleton template changes
  • Re-enable the CI test for validating recipes

HOW to test your changes?

  • Pull down branch
  • Run SHOPIFY_HYDROGEN_FLAG_LOCKFILE_CHECK=false npm run cookbook -- validate to validate all tests
  • Or run SHOPIFY_HYDROGEN_FLAG_LOCKFILE_CHECK=false npm run cookbook -- validate --recipe <RECIPE_NAME> to validate a specific recipe

Checklist

  • I've read the Contributing Guidelines
  • I've considered possible cross-platform impacts (Mac, Linux, Windows)
  • I've added a changeset if this PR contains user-facing or noteworthy changes
  • I've added tests to cover my changes
  • I've added or updated the documentation

@andguy95 andguy95 requested a review from a team as a code owner February 10, 2026 05:50
mockReturnValue() with a mockImplementation() that returns different
directory contents based on which path is being read. This allows
listFilesRecursively to properly traverse the nested structure and
return the correct relative path
templates/skeleton/app/components/Foo.tsx, which matches the ingredient
path in the recipe.
@shopify
Copy link
Contributor

shopify bot commented Feb 10, 2026

Oxygen deployed a preview of your an-fix-cookbook-recipes-2025-10 branch. Details:

Storefront Status Preview link Deployment details Last update (UTC)
Skeleton (skeleton.hydrogen.shop) ✅ Successful (Logs) Preview deployment Inspect deployment February 18, 2026 5:18 AM

Learn more about Hydrogen's GitHub integration.

Copy link
Contributor

@kdaviduik kdaviduik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aside from the --no-verify thing this LGTM!

execSync(`git add .`, {cwd: REPO_ROOT});
execSync(
`git commit --allow-empty -m "Merge ${applyBranch} into ${parsedReferenceBranch.branch}"`,
`git commit --no-verify --allow-empty -m "Merge ${applyBranch} into ${parsedReferenceBranch.branch}"`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the --no-verify added to both of these? Imo we should not disable any of the pre-commit hooks

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kdaviduik the --no-verify was missing for this specific the intermediate commit step that the update command makes.

All the other git add have a --no-verify flag added. When it tries to commit after user resolves conflicts it fails on the patches, but it shouldn't have to when it makes these temp branches and commits to them.

@github-actions
Copy link
Contributor

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset.
If the changes are user-facing and should cause a version bump, run npm run changeset add to track your changes and include them in the next release CHANGELOG.
If you are making simple updates to examples or documentation, you do not need to add a changeset.

`dirent.path` was deprecated in Node.js v20.12.0 in favor of
`dirent.parentPath`, and on Node.js v24 it returns undefined. The fix is
to use `parentPath` falling back to the deprecated `path` for older
versions
New dependencies updated updated zod so we need to update the schema
validation definition
@andguy95 andguy95 requested a review from kdaviduik February 18, 2026 05:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants