From 5611ef9ea9b56ef84f2e17ca394f9e1800e5f9be Mon Sep 17 00:00:00 2001 From: RiskeyL <7a8y@163.com> Date: Mon, 30 Mar 2026 18:40:19 +0800 Subject: [PATCH 1/3] feat: optimize the docs-release-sync skill --- .../skills/dify-docs-release-sync/SKILL.md | 124 +++++++++++------- 1 file changed, 79 insertions(+), 45 deletions(-) diff --git a/.claude/skills/dify-docs-release-sync/SKILL.md b/.claude/skills/dify-docs-release-sync/SKILL.md index dc08f692a..bdcc850d9 100644 --- a/.claude/skills/dify-docs-release-sync/SKILL.md +++ b/.claude/skills/dify-docs-release-sync/SKILL.md @@ -1,27 +1,31 @@ --- name: dify-docs-release-sync description: > - Use when a Dify release milestone is ready and documentation needs - pre-release sync. User provides the milestone name manually. Covers - API reference, help documentation, and environment variable changes. + Use when preparing documentation updates for a Dify release. User provides + two version references to compare (e.g., v1.13.2 and v1.13.3, or v1.13.2 + and main). Covers API reference, help documentation, environment variable + changes, and UI i18n glossary impact. --- # Dify Release Documentation Sync ## Overview -Analyzes a GitHub milestone's merged PRs to identify documentation impact, generates a structured report, then executes updates after user approval. Three tracks: API reference (→ `dify-docs-api-reference`), help documentation (→ `dify-docs-guides`), and environment variables (→ `dify-docs-env-vars`). +Compares code changes between two Dify releases (or a release and current HEAD), identifies documentation impact, generates a structured report, then executes updates after user approval. Three tracks: API reference (→ `dify-docs-api-reference`), help documentation (→ `dify-docs-guides`), and environment variables (→ `dify-docs-env-vars`). -**Input**: Milestone name, provided by the user exactly as it appears on GitHub (e.g., `v1.14.0`). Never auto-detect — always ask if not provided. +**Input**: Two version references, provided by the user. Always ask if not provided. +- Post-release: `v1.13.2` and `v1.13.3` (both tags) +- Pre-release: `v1.13.2` and `main` (tag and branch HEAD) ## Workflow ```dot digraph { rankdir=TB; - "User provides milestone name" -> "Fetch merged PRs from GitHub"; - "Fetch merged PRs from GitHub" -> "Categorize PRs by doc impact"; - "Categorize PRs by doc impact" -> "Generate report"; + "User provides two version refs" -> "Diff changed files between refs"; + "Diff changed files between refs" -> "Fetch PR context for changes"; + "Fetch PR context for changes" -> "Categorize changes by doc impact"; + "Categorize changes by doc impact" -> "Generate report"; "Generate report" -> "Present report, STOP"; "Present report, STOP" -> "User approves / adjusts" [style=dashed]; "User approves / adjusts" -> "Execute API spec updates"; @@ -35,23 +39,37 @@ digraph { ## Phase 1: Analysis -### 1.1 Fetch Milestone PRs +### 1.1 Diff Between Versions -```bash -# Get milestone number from name -MILESTONE_NUM=$(gh api repos/langgenius/dify/milestones --paginate \ - --jq '.[] | select(.title=="MILESTONE_NAME") | .number') +In the Dify codebase (configured as an additional working directory): -# List closed issues/PRs for that milestone -gh api "repos/langgenius/dify/issues?milestone=$MILESTONE_NUM&state=closed&per_page=100" \ - --paginate --jq '.[] | select(.pull_request) | {number, title}' +```bash +git fetch --tags origin +# All changed files between the two versions +git diff .. --stat +# Commit log with PR references for context +git log .. --oneline --grep="(#" ``` -For each PR, fetch changed files and description: +This captures every change between the two versions, regardless of whether PRs were tagged to a milestone. + +For context on specific changes, fetch the relevant PR details: ```bash +# Extract PR numbers from commit messages +git log .. --oneline | grep -oP '#\d+' | sort -u +# Then for each PR gh pr view PR_NUMBER --repo langgenius/dify --json number,title,body,labels,files ``` +**Alternative (milestone-based)**: If the user specifically wants to scope by milestone instead of tags, use: +```bash +MILESTONE_NUM=$(gh api repos/langgenius/dify/milestones --paginate \ + --jq '.[] | select(.title=="MILESTONE_NAME") | .number') +gh api "repos/langgenius/dify/issues?milestone=$MILESTONE_NUM&state=closed&per_page=100" \ + --paginate --jq '.[] | select(.pull_request) | {number, title}' +``` +Note: milestones may miss PRs not tagged to them. Tag comparison is preferred. + ### 1.2 Categorize PRs For each PR, check changed files against these mappings. @@ -134,6 +152,19 @@ Check PRs that touch `web/i18n/en-US/` files: i18n source files: `web/i18n/{en-US,zh-Hans,ja-JP}/` (~30 JSON files each, ~4,875 keys total). Focus on: `common.json`, `app.json`, `workflow.json`, `dataset.json`, `dataset-creation.json`, `dataset-documents.json`—these contain the most documentation-relevant UI labels. +### 1.3 Check Documentation Status + +Before generating the report, verify each identified change against the **current documentation** in this repository branch. For each item: + +1. Read the affected doc page(s) in the docs repo +2. Check whether the code change is already reflected in the documentation +3. Assign a doc status: + - **Already documented**: The current docs accurately describe the new behavior. No update needed. + - **Partially documented**: The docs cover the area but are missing or inaccurate on the specific change. + - **Not yet documented**: The docs don't reflect this change at all. + +This step prevents the report from listing changes that have already been addressed in previous documentation updates. + ## Phase 2: Report Generate the report and **STOP**. Do not execute until the user reviews and approves. @@ -141,43 +172,43 @@ Generate the report and **STOP**. Do not execute until the user reviews and appr ### Report Template ```markdown -# Pre-Release Doc Sync Report: [milestone] +# Doc Sync Report: [from] → [to] ## Summary -- **PRs analyzed**: X merged PRs in milestone -- **API reference impact**: Y PRs → Z spec files -- **Help documentation impact**: W PRs → V doc pages -- **Environment variable impact**: E PRs → F variables -- **UI i18n changes**: G PRs → H glossary entries affected +- **Comparison**: `..` (X commits, Y PRs) +- **API reference impact**: Y PRs → Z spec files (A already documented, B need updates) +- **Help documentation impact**: W PRs → V doc pages (C already documented, D need updates) +- **Environment variable impact**: E PRs → F variables (G already documented, H need updates) +- **UI i18n changes**: I PRs → J glossary entries affected - **No doc impact**: N PRs ## API Reference Changes ### openapi_chat.json / openapi_chatflow.json -| PR | Title | Change Type | Details | -|---|---|---|---| -| #1234 | Add streaming retry | New parameter | `retry_count` on `/chat-messages` | -| #1235 | Fix error handling | Error codes | New `rate_limit_exceeded` on `/chat-messages` | +| PR | Title | Change Type | Details | Doc Status | +|---|---|---|---|---| +| #1234 | Add streaming retry | New parameter | `retry_count` on `/chat-messages` | Not yet documented | +| #1235 | Fix error handling | Error codes | New `rate_limit_exceeded` on `/chat-messages` | Already documented | ### openapi_knowledge.json -| PR | Title | Change Type | Details | -|---|---|---|---| -| #1240 | Add metadata filter | New parameter | `metadata_filter` on list segments | +| PR | Title | Change Type | Details | Doc Status | +|---|---|---|---|---| +| #1240 | Add metadata filter | New parameter | `metadata_filter` on list segments | Not yet documented | ## Help Documentation Changes -| PR | Title | Affected Doc(s) | Priority | Change Needed | -|---|---|---|---|---| -| #1250 | Add semantic chunking | `knowledge/chunking.mdx` | High | Doc describes chunking strategies — new option must be added | -| #1251 | New HTTP node timeout | `workflow/nodes/http.mdx` | Low | Doc doesn't cover timeout config at this level of detail | +| PR | Title | Affected Doc(s) | Priority | Change Needed | Doc Status | +|---|---|---|---|---|---| +| #1250 | Add semantic chunking | `knowledge/chunking.mdx` | High | New chunking option must be added | Not yet documented | +| #1251 | New HTTP node timeout | `workflow/nodes/http.mdx` | Low | Timeout config not covered | Already documented | ## Environment Variable Changes -| PR | Title | Variables | Change Type | Priority | -|---|---|---|---|---| -| #1270 | Add Redis sentinel | `REDIS_SENTINEL_*` (3 new) | New variables | High | -| #1271 | Change default log level | `LOG_LEVEL` default INFO→WARNING | Default change | Medium | +| PR | Title | Variables | Change Type | Priority | Doc Status | +|---|---|---|---|---|---| +| #1270 | Add Redis sentinel | `REDIS_SENTINEL_*` (3 new) | New variables | High | Not yet documented | +| #1271 | Change default log level | `LOG_LEVEL` default INFO→WARNING | Default change | Medium | Already documented | ## UI i18n Changes (Glossary Impact) @@ -200,10 +231,10 @@ After user approval (they may add, remove, or adjust items): ### Codebase Preparation -Checkout the release tag/branch in the Dify codebase (configured as an additional working directory) before auditing: +Checkout the target version in the Dify codebase (configured as an additional working directory) before auditing: ```bash -git fetch --tags -git checkout v1.14.0 # or the release branch +git fetch --tags origin +git checkout # the target release tag or branch ``` ### API Reference Updates @@ -230,7 +261,9 @@ For each affected variable group, use `dify-docs-env-vars` skill: 1. Trace the variable in the release codebase 2. Update `en/self-host/configuration/environments.mdx` 3. Run the verification script to confirm zero mismatches -4. Translation is handled automatically by the Dify workflow on PR push +4. Update `zh/self-host/configuration/environments.mdx` and `ja/self-host/configuration/environments.mdx` with the same changes + +**Important**: `environments.mdx` is in the translation pipeline's ignore list (`tools/translate/config.json`). It is **not** auto-translated on PR push. ZH and JA env var docs must be updated manually. ### Parallel Execution @@ -251,10 +284,11 @@ For each affected variable group, use `dify-docs-env-vars` skill: | Mistake | Fix | |---|---| -| Auto-detecting milestone name | Always ask the user — naming is non-standard | +| Auto-detecting version references | Always ask the user for the two versions to compare | +| Using only milestones | Milestones miss untagged PRs — prefer tag comparison | | Executing before report approval | STOP after report — user must review | | Missing shared endpoint propagation | Fix in one spec → check all 4 app specs | | Ignoring PR description | File paths are heuristic for non-API — description has the real context | | Skipping Pydantic model changes | A model change may affect multiple endpoints — trace which controllers use it | -| Forgetting to checkout release tag | Audit against the release code, not main HEAD | -| Manually translating after EN fixes | Translation is automatic on PR push — never run manual translation scripts | +| Forgetting to checkout target version | Audit against the target release code, not whatever is currently checked out | +| Manually translating after EN fixes | Translation is automatic on PR push — never run manual translation scripts. **Exception**: `environments.mdx` is in the ignore list and must be translated manually. | From d74cc823764c59467a17a7e40f102a98f438a5d2 Mon Sep 17 00:00:00 2001 From: RiskeyL <7a8y@163.com> Date: Mon, 30 Mar 2026 18:40:44 +0800 Subject: [PATCH 2/3] docs: add doc_form validation to knowledge API spec --- en/api-reference/openapi_knowledge.json | 8 ++++---- ja/api-reference/openapi_knowledge.json | 8 ++++---- zh/api-reference/openapi_knowledge.json | 8 ++++---- 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/en/api-reference/openapi_knowledge.json b/en/api-reference/openapi_knowledge.json index a65fa30e7..fbcbb4b92 100644 --- a/en/api-reference/openapi_knowledge.json +++ b/en/api-reference/openapi_knowledge.json @@ -1007,7 +1007,7 @@ } }, "400": { - "description": "- `provider_not_initialize` : No valid model provider credentials found. Please go to Settings -> Model Provider to complete your provider credentials.\n- `invalid_param` : Knowledge base does not exist. / indexing_technique is required.", + "description": "- `provider_not_initialize` : No valid model provider credentials found. Please go to Settings -> Model Provider to complete your provider credentials.\n- `invalid_param` : Knowledge base does not exist. / indexing_technique is required. / Invalid doc_form (must be `text_model`, `hierarchical_model`, or `qa_model`).", "content": { "application/json": { "examples": { @@ -1154,7 +1154,7 @@ } }, "400": { - "description": "- `no_file_uploaded` : Please upload your file.\n- `too_many_files` : Only one file is allowed.\n- `filename_not_exists_error` : The specified filename does not exist.\n- `provider_not_initialize` : No valid model provider credentials found. Please go to Settings -> Model Provider to complete your provider credentials.\n- `invalid_param` : Knowledge base does not exist, external datasets not supported, file too large, unsupported file type, or missing required fields.", + "description": "- `no_file_uploaded` : Please upload your file.\n- `too_many_files` : Only one file is allowed.\n- `filename_not_exists_error` : The specified filename does not exist.\n- `provider_not_initialize` : No valid model provider credentials found. Please go to Settings -> Model Provider to complete your provider credentials.\n- `invalid_param` : Knowledge base does not exist, external datasets not supported, file too large, unsupported file type, missing required fields, or invalid doc_form (must be `text_model`, `hierarchical_model`, or `qa_model`).", "content": { "application/json": { "examples": { @@ -2267,7 +2267,7 @@ } }, "400": { - "description": "- `provider_not_initialize` : No valid model provider credentials found. Please go to Settings -> Model Provider to complete your provider credentials.\n- `invalid_param` : Knowledge base does not exist, or name is required when text is provided.", + "description": "- `provider_not_initialize` : No valid model provider credentials found. Please go to Settings -> Model Provider to complete your provider credentials.\n- `invalid_param` : Knowledge base does not exist, name is required when text is provided, or invalid doc_form (must be `text_model`, `hierarchical_model`, or `qa_model`).", "content": { "application/json": { "examples": { @@ -2421,7 +2421,7 @@ } }, "400": { - "description": "- `too_many_files` : Only one file is allowed.\n- `filename_not_exists_error` : The specified filename does not exist.\n- `provider_not_initialize` : No valid model provider credentials found. Please go to Settings -> Model Provider to complete your provider credentials.\n- `invalid_param` : Knowledge base does not exist, external datasets not supported, file too large, or unsupported file type.", + "description": "- `too_many_files` : Only one file is allowed.\n- `filename_not_exists_error` : The specified filename does not exist.\n- `provider_not_initialize` : No valid model provider credentials found. Please go to Settings -> Model Provider to complete your provider credentials.\n- `invalid_param` : Knowledge base does not exist, external datasets not supported, file too large, unsupported file type, or invalid doc_form (must be `text_model`, `hierarchical_model`, or `qa_model`).", "content": { "application/json": { "examples": { diff --git a/ja/api-reference/openapi_knowledge.json b/ja/api-reference/openapi_knowledge.json index c5f92c086..dd8064013 100644 --- a/ja/api-reference/openapi_knowledge.json +++ b/ja/api-reference/openapi_knowledge.json @@ -1007,7 +1007,7 @@ } }, "400": { - "description": "- `provider_not_initialize` : 有効なモデルプロバイダーの認証情報が見つかりません。設定 → モデルプロバイダーで認証情報を完了してください。\n- `invalid_param` : ナレッジベースが存在しません。/ indexing_technique は必須です。", + "description": "- `provider_not_initialize` : 有効なモデルプロバイダーの認証情報が見つかりません。設定 → モデルプロバイダーで認証情報を完了してください。\n- `invalid_param` : ナレッジベースが存在しません。/ indexing_technique は必須です。/ doc_form が無効です（`text_model`、`hierarchical_model`、または `qa_model` のいずれかである必要があります）。", "content": { "application/json": { "examples": { @@ -1154,7 +1154,7 @@ } }, "400": { - "description": "- `no_file_uploaded` : ファイルをアップロードしてください。\n- `too_many_files` : ファイルは 1 つのみ許可されています。\n- `filename_not_exists_error` : 指定されたファイル名が存在しません。\n- `provider_not_initialize` : 有効なモデルプロバイダーの認証情報が見つかりません。設定 → モデルプロバイダーで認証情報を完了してください。\n- `invalid_param` : ナレッジベースが存在しない、外部データセットは非対応、ファイルが大きすぎる、サポートされていないファイルタイプ、または必須フィールドが不足しています。", + "description": "- `no_file_uploaded` : ファイルをアップロードしてください。\n- `too_many_files` : ファイルは 1 つのみ許可されています。\n- `filename_not_exists_error` : 指定されたファイル名が存在しません。\n- `provider_not_initialize` : 有効なモデルプロバイダーの認証情報が見つかりません。設定 → モデルプロバイダーで認証情報を完了してください。\n- `invalid_param` : ナレッジベースが存在しない、外部データセットは非対応、ファイルが大きすぎる、サポートされていないファイルタイプ、必須フィールドが不足している、または doc_form が無効です（`text_model`、`hierarchical_model`、または `qa_model` のいずれかである必要があります）。", "content": { "application/json": { "examples": { @@ -2267,7 +2267,7 @@ } }, "400": { - "description": "- `provider_not_initialize` : 有効なモデルプロバイダーの認証情報が見つかりません。設定 → モデルプロバイダーで認証情報を完了してください。\n- `invalid_param` : ナレッジベースが存在しない、またはテキスト指定時は name が必須です。", + "description": "- `provider_not_initialize` : 有効なモデルプロバイダーの認証情報が見つかりません。設定 → モデルプロバイダーで認証情報を完了してください。\n- `invalid_param` : ナレッジベースが存在しない、テキスト指定時は name が必須、または doc_form が無効です（`text_model`、`hierarchical_model`、または `qa_model` のいずれかである必要があります）。", "content": { "application/json": { "examples": { @@ -2421,7 +2421,7 @@ } }, "400": { - "description": "- `too_many_files` : ファイルは 1 つのみ許可されています。\n- `filename_not_exists_error` : 指定されたファイル名が存在しません。\n- `provider_not_initialize` : 有効なモデルプロバイダーの認証情報が見つかりません。設定 → モデルプロバイダーで認証情報を完了してください。\n- `invalid_param` : ナレッジベースが存在しない、外部データセットは非対応、ファイルが大きすぎる、またはサポートされていないファイルタイプです。", + "description": "- `too_many_files` : ファイルは 1 つのみ許可されています。\n- `filename_not_exists_error` : 指定されたファイル名が存在しません。\n- `provider_not_initialize` : 有効なモデルプロバイダーの認証情報が見つかりません。設定 → モデルプロバイダーで認証情報を完了してください。\n- `invalid_param` : ナレッジベースが存在しない、外部データセットは非対応、ファイルが大きすぎる、サポートされていないファイルタイプ、または doc_form が無効です（`text_model`、`hierarchical_model`、または `qa_model` のいずれかである必要があります）。", "content": { "application/json": { "examples": { diff --git a/zh/api-reference/openapi_knowledge.json b/zh/api-reference/openapi_knowledge.json index 2473cdd63..eccb8ac22 100644 --- a/zh/api-reference/openapi_knowledge.json +++ b/zh/api-reference/openapi_knowledge.json @@ -1007,7 +1007,7 @@ } }, "400": { - "description": "- `provider_not_initialize` : 未找到有效的模型提供商凭据。请前往设置 -> 模型提供商完成凭据配置。\n- `invalid_param` : 知识库不存在。/ indexing_technique 为必填项。", + "description": "- `provider_not_initialize` : 未找到有效的模型提供商凭据。请前往设置 -> 模型提供商完成凭据配置。\n- `invalid_param` : 知识库不存在。/ indexing_technique 为必填项。/ doc_form 无效（必须为 `text_model`、`hierarchical_model` 或 `qa_model`）。", "content": { "application/json": { "examples": { @@ -1154,7 +1154,7 @@ } }, "400": { - "description": "- `no_file_uploaded` : 请上传文件。\n- `too_many_files` : 仅允许上传一个文件。\n- `filename_not_exists_error` : 指定的文件名不存在。\n- `provider_not_initialize` : 未找到有效的模型提供商凭据。请前往设置 -> 模型提供商完成凭据配置。\n- `invalid_param` : 知识库不存在、不支持外部数据集、文件过大、不支持的文件类型或缺少必填字段。", + "description": "- `no_file_uploaded` : 请上传文件。\n- `too_many_files` : 仅允许上传一个文件。\n- `filename_not_exists_error` : 指定的文件名不存在。\n- `provider_not_initialize` : 未找到有效的模型提供商凭据。请前往设置 -> 模型提供商完成凭据配置。\n- `invalid_param` : 知识库不存在、不支持外部数据集、文件过大、不支持的文件类型、缺少必填字段或 doc_form 无效（必须为 `text_model`、`hierarchical_model` 或 `qa_model`）。", "content": { "application/json": { "examples": { @@ -2267,7 +2267,7 @@ } }, "400": { - "description": "- `provider_not_initialize` : 未找到有效的模型提供商凭据。请前往设置 -> 模型提供商完成凭据配置。\n- `invalid_param` : 知识库不存在，或提供文本时 name 为必填项。", + "description": "- `provider_not_initialize` : 未找到有效的模型提供商凭据。请前往设置 -> 模型提供商完成凭据配置。\n- `invalid_param` : 知识库不存在、提供文本时 name 为必填项或 doc_form 无效（必须为 `text_model`、`hierarchical_model` 或 `qa_model`）。", "content": { "application/json": { "examples": { @@ -2421,7 +2421,7 @@ } }, "400": { - "description": "- `too_many_files` : 仅允许上传一个文件。\n- `filename_not_exists_error` : 指定的文件名不存在。\n- `provider_not_initialize` : 未找到有效的模型提供商凭据。请前往设置 -> 模型提供商完成凭据配置。\n- `invalid_param` : 知识库不存在、不支持外部数据集、文件过大或不支持的文件类型。", + "description": "- `too_many_files` : 仅允许上传一个文件。\n- `filename_not_exists_error` : 指定的文件名不存在。\n- `provider_not_initialize` : 未找到有效的模型提供商凭据。请前往设置 -> 模型提供商完成凭据配置。\n- `invalid_param` : 知识库不存在、不支持外部数据集、文件过大、不支持的文件类型或 doc_form 无效（必须为 `text_model`、`hierarchical_model` 或 `qa_model`）。", "content": { "application/json": { "examples": { From d33f793657f8219173f80de2b53e31e2da5e88d0 Mon Sep 17 00:00:00 2001 From: RiskeyL <7a8y@163.com> Date: Mon, 30 Mar 2026 18:41:17 +0800 Subject: [PATCH 3/3] docs: update AI Credits/Default Model Settings terminology --- .claude/skills/dify-docs-release-sync/SKILL.md | 4 ++-- en/use-dify/getting-started/quick-start.mdx | 6 +++--- ja/use-dify/getting-started/quick-start.mdx | 4 ++-- tools/translate/termbase_i18n.md | 6 ++++-- writing-guides/glossary.md | 6 ++++-- 5 files changed, 15 insertions(+), 11 deletions(-) diff --git a/.claude/skills/dify-docs-release-sync/SKILL.md b/.claude/skills/dify-docs-release-sync/SKILL.md index bdcc850d9..a65b0a147 100644 --- a/.claude/skills/dify-docs-release-sync/SKILL.md +++ b/.claude/skills/dify-docs-release-sync/SKILL.md @@ -33,7 +33,7 @@ digraph { "User approves / adjusts" -> "Execute env var updates"; "Execute API spec updates" -> "Auto-translated on PR push"; "Execute help doc updates" -> "Auto-translated on PR push"; - "Execute env var updates" -> "Auto-translated on PR push"; + "Execute env var updates" -> "Manually update ZH/JA (not auto-translated)"; } ``` @@ -56,7 +56,7 @@ This captures every change between the two versions, regardless of whether PRs w For context on specific changes, fetch the relevant PR details: ```bash # Extract PR numbers from commit messages -git log .. --oneline | grep -oP '#\d+' | sort -u +git log .. --oneline | grep -oE '#[0-9]+' | sort -u # Then for each PR gh pr view PR_NUMBER --repo langgenius/dify --json number,title,body,labels,files ``` diff --git a/en/use-dify/getting-started/quick-start.mdx b/en/use-dify/getting-started/quick-start.mdx index d8e3036df..707434cb7 100644 --- a/en/use-dify/getting-started/quick-start.mdx +++ b/en/use-dify/getting-started/quick-start.mdx @@ -23,10 +23,10 @@ The complete workflow is shown below. Feel free to refer back to this as you bui Go to [Dify Cloud](https://cloud.dify.ai) and sign up for free. - New accounts on the Sandbox plan include 200 message credits for calling models from providers like OpenAI, Anthropic, and Gemini. + New accounts on the Sandbox plan include 200 AI credits for calling models from providers like OpenAI, Anthropic, and Gemini. - Message credits are a one-time allocation and don't renew monthly. + AI credits are a one-time allocation and don't renew monthly. @@ -40,7 +40,7 @@ The complete workflow is shown below. Feel free to refer back to this as you bui - 1. In the top-right corner of the **Model Provider** page, click **System Model Settings**. + 1. In the top-right corner of the **Model Provider** page, click **Default Model Settings**. 2. Set the **System Reasoning Model** to `gpt-5.2`. This becomes the default model in the workflow. diff --git a/ja/use-dify/getting-started/quick-start.mdx b/ja/use-dify/getting-started/quick-start.mdx index 643758963..b5e4da863 100644 --- a/ja/use-dify/getting-started/quick-start.mdx +++ b/ja/use-dify/getting-started/quick-start.mdx @@ -25,10 +25,10 @@ icon: "forward" [Dify Cloud](https://cloud.dify.ai)にアクセスして無料でサインアップします。 - Sandboxプランの新しいアカウントには、OpenAI、Anthropic、Geminiなどのプロバイダーからモデルを呼び出すための200メッセージクレジットが含まれています。 + Sandboxプランの新しいアカウントには、OpenAI、Anthropic、Geminiなどのプロバイダーからモデルを呼び出すための200 AI クレジットが含まれています。 - メッセージクレジットは1回限りの割り当てであり、毎月更新されません。 + AI クレジットは1回限りの割り当てであり、毎月更新されません。 diff --git a/tools/translate/termbase_i18n.md b/tools/translate/termbase_i18n.md index ea74e60c0..b23d33463 100644 --- a/tools/translate/termbase_i18n.md +++ b/tools/translate/termbase_i18n.md @@ -185,14 +185,16 @@ | API Extension | API 扩展 | API 拡張 | | Billing | 账单 | 請求 | | Integrations | 集成 | 統合 | -| System Model Settings | 系统模型设置 | システムモデル設定 | +| Default Model Settings | 默认模型设置 | デフォルトモデル設定 | | System Reasoning Model | 系统推理模型 | システム推論モデル | | Embedding Model | Embedding 模型 | 埋め込みモデル | | Rerank Model | Rerank 模型 | Rerank モデル | | Speech-to-Text Model | 语音转文本模型 | 音声-to-テキストモデル | | Text-to-Speech Model | 文本转语音模型 | テキスト-to-音声モデル | | Load Balancing | 负载均衡 | 負荷分散 | -| Message Credits | 消息额度 | クレジット | +| AI Credits | AI Credits | AI クレジット | +| Usage Priority | 使用优先级 | 利用優先度 | +| API Key | API 密钥 | API キー | ### Workspace Roles diff --git a/writing-guides/glossary.md b/writing-guides/glossary.md index a5544a202..e9011968c 100644 --- a/writing-guides/glossary.md +++ b/writing-guides/glossary.md @@ -192,14 +192,16 @@ Terms in this section must match the Dify product interface exactly. When these | API Extension | API 扩展 | API 拡張 | common.settings.apiBasedExtension | | | Billing | 账单 | 請求 | common.settings.billing | | | Integrations | 集成 | 統合 | common.settings.integrations | | -| System Model Settings | 系统模型设置 | システムモデル設定 | common.modelProvider.systemModelSettings | | +| Default Model Settings | 默认模型设置 | システムモデル設定 | common.modelProvider.systemModelSettings | Renamed from "System Model Settings" in v1.13.1. EN/ZH UI updated; JA UI still shows "システムモデル設定" until i18n update. Planned JA label:「デフォルトモデル設定」. | | System Reasoning Model | 系统推理模型 | システム推論モデル | common.modelProvider.systemReasoningModel.key | | | Embedding Model | Embedding 模型 | 埋め込みモデル | common.modelProvider.embeddingModel.key | | | Rerank Model | Rerank 模型 | Rerank モデル | common.modelProvider.rerankModel.key | | | Speech-to-Text Model | 语音转文本模型 | 音声-to-テキストモデル | common.modelProvider.speechToTextModel.key | | | Text-to-Speech Model | 文本转语音模型 | テキスト-to-音声モデル | common.modelProvider.ttsModel.key | | | Load Balancing | 负载均衡 | 負荷分散 | common.modelProvider.loadBalancing | | -| Message Credits | 消息额度 | クレジット | common.modelProvider.credits | | +| AI Credits | AI Credits | AI クレジット | common.modelProvider.quota | Renamed from "Message Credits" in v1.13.1. ZH uses English "AI Credits" in UI. | +| Usage Priority | 使用优先级 | 使用優先度 | common.modelProvider.card.usagePriority | New in v1.13.1. Determines fallback order between API Key and AI Credits. | +| API Key | API Key | API キー | common.modelProvider.card.apiKeyOption | New in v1.13.1. Model provider credential option alongside AI Credits. | ### Workspace Roles