docs: sync V4.16.2 release notes - #7620
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
✅ Docs preview deployed 🔗 👀 Click here to visit preview 🕒 Time: 2026-08-31 18:26:49 (UTC+8) |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8b977df5bb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 11. Fixed legacy workflow fields in older App templates so they can be read using the current structure. | ||
| 12. Fixed fuzzy file extension matching that could show a DOC icon for a Markdown filename containing text such as DOCX. Added icon mappings for the new document formats and a dedicated EPUB icon. | ||
| 13. Fixed chat configuration validation failures when `valueType` is empty or `null` in historical App Variables. FastGPT now derives `valueType` from the Variable input type when loading or saving chat configuration, falls back to `any` when the type cannot be mapped or the value is invalid, and runs Zod validation before saving. Existing data does not require an additional cleanup script. | ||
| 10. Fixed legacy workflow fields in older App templates so they can be read using the current structure. |
There was a problem hiding this comment.
The removed entry still describes code shipped in this tree: CancelAccountPage.tsx passes the server-returned status.verificationMethod into VerificationPanel instead of resolving it again on the client, and the cancellation schema still persists notificationStatus. No later commit between that fix and this commit changes those implementation files, so removing the entry makes the V4.16.2 notes omit a fix users actually receive; restore it in both locales or revert the implementation as well.
Useful? React with 👍 / 👎.
What changed
Validation