Commit 03ff1b5d by Archer Committed by GitHub

doc (#7211)

parent 402ad3ff
---
title: 'V4.15.0-beta7'
title: 'V4.15.0-beta7 (In Progress)'
description: 'FastGPT V4.15.0-beta7 Release Notes'
---
## 📦 Upgrade Guide
### 1. Run the Workflow V1 to V2 Migration
### 1. Run the Workflow V1 to V2 Migration (Optional)
Only users who have deployed a FastGPT version earlier than `<4.8` need to run this step.
Starting from V4.15.0-beta7, workflow save payloads use the V2 structure consistently. Historical `apps.modules` and `app_versions.nodes` records may still use the V1 structure. Run the V1 -> V2 migration first, then run the V2 dirty-data cleanup in the next step.
......@@ -106,11 +108,11 @@ The response includes separate statistics for `apps`, `appVersions`, and `total`
### 3. Update Images
- Update the fastgpt-app (FastGPT main service) image tag to v4.15.0-beta7.
- Update the fastgpt-pro (FastGPT commercial edition) image tag to v4.15.0-beta7.
- Update the fastgpt-plugin image tag to v1.0.0-beta7.
- Update the fastgpt-app (FastGPT main service) image tag to v4.15.0.
- Update the fastgpt-pro (FastGPT commercial edition) image tag to v4.15.0.
## 🐛 Fixes
1. Fixed historical V1 workflow data that could fail validation under the new save payload structure.
2. Fixed dirty `FlowNodeInputTypeEnum.*`, `FlowNodeOutputTypeEnum.*`, and `WorkflowIOValueTypeEnum.*` expression strings in workflow nodes that could break input rendering and IO type checks.
3. Fixed AgentV2 MCP not being able to retrieve schemas.
---
title: 'V4.15.0-beta7'
title: 'V4.15.0-beta7(进行中)'
description: 'FastGPT V4.15.0-beta7 更新说明'
---
......@@ -108,9 +108,8 @@ curl -X POST 'https://你的域名/api/admin/dataClean/initWorkflowData' \
### 3. 更新镜像
- 更新 fastgpt-app(fastgpt 主服务) 镜像 tag: v4.15.0-beta7
- 更新 fastgpt-pro(fastgpt 商业版) 镜像 tag: v4.15.0-beta7
- 更新 fastgpt-plugin 镜像 tag: v1.0.0-beta7
- 更新 fastgpt-app(fastgpt 主服务) 镜像 tag: v4.15.0
- 更新 fastgpt-pro(fastgpt 商业版) 镜像 tag: v4.15.0
## 🐛 修复
......
......@@ -294,7 +294,7 @@
"content/self-host/upgrading/4-14/4149.en.mdx": "2026-04-26T21:08:47+08:00",
"content/self-host/upgrading/4-14/4149.mdx": "2026-04-26T21:08:47+08:00",
"content/self-host/upgrading/4-15/41500.en.mdx": "2026-06-29T00:47:43+08:00",
"content/self-host/upgrading/4-15/41500.mdx": "2026-06-29T21:48:35+08:00",
"content/self-host/upgrading/4-15/41500.mdx": "2026-06-29T23:38:28+08:00",
"content/self-host/upgrading/4-15/41501.mdx": "2026-06-23T21:09:39+08:00",
"content/self-host/upgrading/4-15/41502.en.mdx": "2026-05-25T11:21:30+08:00",
"content/self-host/upgrading/4-15/41502.mdx": "2026-06-23T13:54:06+08:00",
......@@ -306,6 +306,8 @@
"content/self-host/upgrading/4-15/41505.mdx": "2026-06-29T10:45:58+08:00",
"content/self-host/upgrading/4-15/41506.en.mdx": "2026-06-29T00:47:43+08:00",
"content/self-host/upgrading/4-15/41506.mdx": "2026-06-29T00:47:43+08:00",
"content/self-host/upgrading/4-15/41507.en.mdx": "2026-06-29T23:38:28+08:00",
"content/self-host/upgrading/4-15/41507.mdx": "2026-06-29T23:38:28+08:00",
"content/self-host/upgrading/outdated/40.en.mdx": "2026-04-26T21:08:47+08:00",
"content/self-host/upgrading/outdated/40.mdx": "2026-04-26T21:08:47+08:00",
"content/self-host/upgrading/outdated/41.en.mdx": "2026-04-26T21:08:47+08:00",
......@@ -446,6 +448,6 @@
"content/self-host/upgrading/outdated/499.mdx": "2026-05-07T15:06:40+08:00",
"content/self-host/upgrading/upgrade-intruction.en.mdx": "2026-04-26T21:08:47+08:00",
"content/self-host/upgrading/upgrade-intruction.mdx": "2026-04-26T21:08:47+08:00",
"content/toc.en.mdx": "2026-06-29T21:48:35+08:00",
"content/toc.mdx": "2026-06-29T21:48:35+08:00"
"content/toc.en.mdx": "2026-06-29T23:38:28+08:00",
"content/toc.mdx": "2026-06-29T23:38:28+08:00"
}
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or sign in to comment