Update migration_guide.txt

migration_guide.txt

@@ -1,5 +1,11 @@
 # Gradio 6 Migration Guide
 
+We are excited to release Gradio 6, the latest major version of the Gradio library. Gradio 6 is significantly more performant, lighter, and easier to customize than previous versions of Gradio. The Gradio team is only planning on maintaining future versions of Gradio 6 so we encourage all developers to migrate to Gradio 6.x.
+
+Gradio 6 includes several breaking changes that were made in order to standardize the Python API. This migration guide lists the breaking changes and the specific code changes needed in order to migrate. The easiest way to know whether you need to make changes is to upgrade your Gradio app to 5.50 (`pip install --upgrade gradio==5.50`). Gradio 5.50 emits deprecation warnings for any parameters removed in Gradio 6, allowing you to know whether your Gradio app will be compatible with Gradio 6.
+
+Here, we walk through the breaking changes that were introduced in Gradio 6. Code snippets are provided, allowing you to migrate your code easily to Gradio 6. You can also copy-paste this document as Markdown if you are using an LLM to help migrate your code. 
+
 ## App-level Changes
 
 ### App-level parameters have been moved from `Blocks` to `launch()`
@@ -312,6 +318,50 @@ history = [
 
 This structured format allows for multimodal content (text, images, files, etc.) in chat messages, making it consistent with OpenAI's API format. All files uploaded in a single message are grouped together in the `content` array along with any text content.
 
+### `cache_examples` parameter updated and `cache_mode` introduced
+
+The `cache_examples` parameter (used in `Interface`, `ChatInterface`, and `Examples`) no longer accepts the string value `"lazy"`. It now strictly accepts boolean values (`True` or `False`). To control the caching strategy, a new `cache_mode` parameter has been introduced.
+
+**In Gradio 5.x:**
+- `cache_examples` accepted `True`, `False`, or `"lazy"`.
+
+**In Gradio 6.x:**
+- `cache_examples` only accepts `True` or `False`.
+- `cache_mode` accepts `"eager"` (default) or `"lazy"`.
+
+**Before (Gradio 5.x):**
+
+```python
+import gradio as gr
+
+demo = gr.Interface(
+    fn=predict, 
+    inputs="text", 
+    outputs="text", 
+    examples=["Hello", "World"],
+    cache_examples="lazy"
+)
+```
+
+**After (Gradio 6.x):**
+
+You must now set `cache_examples=True` and specify the mode separately:
+
+```python
+import gradio as gr
+
+demo = gr.Interface(
+    fn=predict, 
+    inputs="text", 
+    outputs="text", 
+    examples=["Hello", "World"],
+    cache_examples=True,
+    cache_mode="lazy"
+)
+```
+
+If you previously used `cache_examples=True` (which implied eager caching), no changes are required, as `cache_mode` defaults to `"eager"`.
+
 ## Component-level Changes
 
 ### `gr.Video` no longer accepts tuple values for video and subtitles
@@ -503,6 +553,7 @@ chatbot = gr.Chatbot(allow_tags=["thinking", "tool_call"])
 This will only preserve `<thinking>` and `<tool_call>` tags while removing all other custom tags.
 
 
+
 ### Other removed component parameters
 
 Several component parameters have been removed in Gradio 6.0. These parameters were previously deprecated and have now been fully removed.
@@ -803,6 +854,21 @@ slider = gr.Slider(show_reset_button=True)
 slider = gr.Slider(buttons=["reset"])
 ```
 
+
+## CLI Changes
+
+### `gradio sketch` command removed
+
+The `gradio sketch` command-line tool has been deprecated and completely removed in Gradio 6. This tool was used to create Gradio apps through a visual interface.
+
+**In Gradio 5.x:**
+- You could run `gradio sketch` to launch an interactive GUI for building Gradio apps
+- The tool would generate Python code visually
+
+**In Gradio 6.x:**
+- The `gradio sketch` command has been removed
+- Running `gradio sketch` will raise a `DeprecationWarning`
+
 ## Python Client Changes
 
 ### `hf_token` parameter renamed to `token` in `Client`