fix: update GAIE recipe to reflect frontend image release

[tmonty12]

Overview:

The Dynamo frontend image will not be released in 0.7.0. This PR updates documentation to reflect that and point towards instructions for building Dynamo EPP image.

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Documentation
  • Updated deployment guidance to clarify that the frontend Dynamo image will not be included in the 0.7.0 release.
  • Added clear, prominent instructions for users to build their own custom Dynamo EPP image.
  • Standardized build guidance across deployment documentation sections.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Documentation updates to two README files informing users that the frontend Dynamo image will not be included in the 0.7.0 release. Changes optional guidance to mandatory instructions for building a custom EPP image, with added prominent warnings and standardized phrasing throughout.

Changes

Cohort / File(s)	Summary
Documentation Updates deploy/inference-gateway/README.md, recipes/README.md	Replaces commented export instructions with prominent warnings that the frontend image is unavailable in 0.7.0 release. Converts optional guidance ("can build") to imperative instructions ("Build your own"). Standardizes section headers and adds bold highlighted notes in multiple locations emphasizing the requirement to build a custom EPP image.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

• Documentation-only changes with no code logic
• Straightforward content rewording and warning additions
• Consistent pattern repeated across sections

Poem

🐰 Hark! No frontend in the 0.7.0 stash,
Build your own EPP image, no time to dash,
Bold warnings now guide each eager paw,
Mandatory instructions, that's the law!

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating GAIE recipe documentation to reflect that the frontend image will not be released in 0.7.0.
Description check	✅ Passed	The description includes the Overview section with clear explanation, but the Details and Where should the reviewer start sections are incomplete with only placeholder comments.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

deploy/inference-gateway/README.md (1)

114-115: Standardize warning phrasing across the file.

The file contains two warnings about the 0.7.0 release (lines 114 and 150) with inconsistent formatting and terminology:

• Line 114 uses ⚠️ Note: (unbolded) and references "Build the custom EPP image" section
• Line 150 uses **⚠️ Important:** (bolded) and refers to "steps below"

Since the PR objectives emphasize standardized phrasing throughout the documentation, consider aligning these warnings to use the same prefix style, emphasis level, and terminology. Additionally, clarify whether both warnings are necessary or if one can be consolidated.

Also applies to: 150-154

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b5db4e7 and 37d6dc1.

📒 Files selected for processing (2)

• deploy/inference-gateway/README.md (2 hunks)
• recipes/README.md (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). (5)

• GitHub Check: operator (amd64)
• GitHub Check: trtllm (amd64)
• GitHub Check: vllm (arm64)
• GitHub Check: vllm (amd64)
• GitHub Check: Build and Test - dynamo

🔇 Additional comments (1)

recipes/README.md (1)

189-191: Verify the anchor link to the build instructions section.

The reference to #1-build-the-custom-epp-image should be verified to ensure it matches the markdown heading created by the "##### 1. Build the custom EPP image #####" section in deploy/inference-gateway/README.md. Most markdown renderers generate anchors by converting to lowercase and replacing spaces with hyphens, but this depends on the specific renderer used.