fix: propagate publish release flag through Go agent endpoints (#17347)

docs/guides/agent/agent_quickstarts/sandbox_quickstart.md

@@ -122,7 +122,7 @@ docker compose -f docker-compose.yml down
 docker compose -f docker-compose.yml up -d
 ```
 
-## Running with RAGFlow 
+## Running with RAGFlow
 
 1. Verify that gVisor is properly installed and operational.
 

docs/guides/dataset/add_data_source/add_github_repo.md

@@ -48,7 +48,7 @@ Once your GitHub token is ready, register the external data source within your R
     - **Access token:** Paste the PAT generated in section 1.
     - **Include Pull Request** Whether to include pull requests in the selected repo.
     - **Include Issues** Whether to include issues in the selected repo.
-4. Click **Save** to confirm your changes.  
+4. Click **Save** to confirm your changes.
    *RAGFlow validates the connection immediately.*
 
 ![GitHub](https://raw.githubusercontent.com/infiniflow/ragflow-docs/main/images/github.jpg)
@@ -66,4 +66,4 @@ Finally, link the connector to a specific knowledge base to begin the RAG proces
 3. **Select GitHub source:** Pick the connector you just created.
 4. **Trigger initial sync:** - The files from the repo will appear in your file list.
     - Select the files and click **Run/parsing**.
-    - **Parser selection:** For codebases, use the **"Naive"** parser for general text extraction or a specific code-aware template if available in your current version.
+    - **Parser selection:** For codebases, use the **"Naive"** parser for general text extraction or a specific code-aware template if available in your current version.

docs/guides/dataset/advanced/construct_knowledge_graph.md

@@ -65,7 +65,7 @@ In a knowledge graph, a community is a cluster of entities linked by relationshi
 ## Quickstart
 
 1. Navigate to the **Configuration** page of your dataset and update:
-   
+
    - Entity types: *Required* - Specifies the entity types in the knowledge graph to generate. You don't have to stick with the default, but you need to customize them for your documents.
    - Method: *Optional*
    - Entity resolution: *Optional*
@@ -76,12 +76,12 @@ In a knowledge graph, a community is a cluster of entities linked by relationshi
 
    *You can click the pause button in the dropdown to halt the build process when necessary.*
 
-3. Go back to the **Configuration** page:  
-   
+3. Go back to the **Configuration** page:
+
    *Once a knowledge graph is generated, the **Knowledge graph** field changes from `Not generated` to `Generated at a specific timestamp`. You can delete it by clicking the recycle bin button to the right of the field.*
 
 4. To use the created knowledge graph, do either of the following:
-   
+
    - In the **Chat setting** panel of your chat app, switch on the **Use knowledge graph** toggle.
    - If you are using an agent, click the **Retrieval** agent component to specify the dataset(s) and switch on the **Use knowledge graph** toggle.
 
@@ -101,4 +101,4 @@ All chunks of the created knowledge graph are stored in RAGFlow's document engin
 
 ### How to export a created knowledge graph?
 
-Nope. Exporting a created knowledge graph is not supported. If you still consider this feature essential, please [raise an issue](https://github.com/infiniflow/ragflow/issues) explaining your use case and its importance.
+Nope. Exporting a created knowledge graph is not supported. If you still consider this feature essential, please [raise an issue](https://github.com/infiniflow/ragflow/issues) explaining your use case and its importance.

docs/guides/dataset/advanced/enable_raptor.md

@@ -78,7 +78,7 @@ A random seed. Click **+** to change the seed value.
 ## Quickstart
 
 1. Navigate to the **Configuration** page of your dataset and update:
-   
+
    - Prompt: *Optional* - We recommend that you keep it as-is until you understand the mechanism behind.
    - Max token: *Optional*
    - Threshold: *Optional*
@@ -88,8 +88,8 @@ A random seed. Click **+** to change the seed value.
 
    *You can click the pause button in the dropdown to halt the build process when necessary.*
 
-3. Go back to the **Configuration** page:  
-   
+3. Go back to the **Configuration** page:
+
    *The **RAPTOR** field changes from `Not generated` to `Generated at a specific timestamp` when a RAPTOR hierarchical tree structure is generated. You can delete it by clicking the recycle bin button to the right of the field.*
 
 4. Once a RAPTOR hierarchical tree structure is generated, your chat assistant and **Retrieval** agent component will use it for retrieval as a default.

docs/guides/dataset/advanced/extract_table_of_contents.md

@@ -30,7 +30,7 @@ The system's default chat model is used to summarize clustered content. Before p
 2. Enable **PageIndex**.
 
 3. To use this technique during retrieval, do either of the following:
-   
+
    - In the **Chat setting** panel of your chat app, switch on the **PageIndex** toggle.
    - If you are using an Agent, click the **Retrieval** agent component to specify the dataset(s) and switch on the **PageIndex** toggle.
 
@@ -38,4 +38,4 @@ The system's default chat model is used to summarize clustered content. Before p
 
 ### Will previously parsed files be searched using the directory enhancement feature once I enable `PageIndex`?
 
-No. Only files parsed after you enable **PageIndex** will be searched using the directory enhancement feature. To apply this feature to files parsed before enabling **PageIndex**, you must reparse them.
+No. Only files parsed after you enable **PageIndex** will be searched using the directory enhancement feature. To apply this feature to files parsed before enabling **PageIndex**, you must reparse them.

docs/guides/dataset/configure_child_chunking_strategy.md

@@ -33,4 +33,4 @@ Through this dual-layer structure of "precise localization + contextual suppleme
 
 3. This configuration applies to the **Chunker** component when it comes to ingestion pipeline settings:
 
-![](https://raw.githubusercontent.com/infiniflow/ragflow-docs/main/images/child_chunking_chunker.png)
+![](https://raw.githubusercontent.com/infiniflow/ragflow-docs/main/images/child_chunking_chunker.png)

docs/guides/dataset/set_metadata.md

@@ -31,4 +31,4 @@ Ensure that your metadata is in JSON format; otherwise, your updates will not be
 
 ### Can I set metadata for multiple documents at once?
 
-From v0.23.0 onwards, you can set metadata for each document individually or have the LLM auto-generate metadata for multiple files. See [Extract metadata](./advanced/auto_metadata.md) for details.
+From v0.23.0 onwards, you can set metadata for each document individually or have the LLM auto-generate metadata for multiple files. See [Extract metadata](./advanced/auto_metadata.md) for details.

docs/guides/models/llm_api_key_setup.md

@@ -11,7 +11,7 @@ RAGFlow model provider management allows you to connect online models, local mod
 
 ## Get model API key
 
-RAGFlow supports most mainstream LLMs. Please refer to [Supported Models](../../guides/models/supported_models.mdx) for a complete list of supported models. You will need to apply for your model API key online. 
+RAGFlow supports most mainstream LLMs. Please refer to [Supported Models](../../guides/models/supported_models.mdx) for a complete list of supported models. You will need to apply for your model API key online.
 
 :::note
 If you find your online LLM is not on the list, don't feel disheartened. The list is expanding, and you can [file a feature request](https://github.com/infiniflow/ragflow/issues/new?assignees=&labels=feature+request&projects=&template=feature_request.yml&title=%5BFeature+Request%5D%3A+) with us! Alternatively, if you have customized or locally-deployed models, you can [bind them to RAGFlow using Ollama, Xinference, or LocalAI](./deploy_local_llm.mdx).
@@ -119,4 +119,4 @@ The following model types usually work together for retrieval and generation:
 
 ## Supported model list
 
-See [Supported Models](./supported_models.mdx).
+See [Supported Models](./supported_models.mdx).