Summarize the weekly product update logs, and the latest releases can be checked on our blog.
NocoBase is currently updated with three branches: main , next and develop.

main:The most stable version to date, recommended for installation;next:Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It’s mainly for test users to collect feedback and optimize functions further. Ideal for test users who want to experience new features early and give feedback;develop:Alpha version, contains the latest feature code, may be incomplete or unstable, mainly for internal dev and rapid iteration. Suited for tech users interested in product’s cutting-edge, but with potential issues and incomplete functions. Not for production use.
main

v2.0.37
Release date: 2026-04-14
🚀 Improvements
-
[undefined]
-
[client] add form required verification switch (#9060) by @jiannx
🐛 Bug Fixes
- [utils] Add security control for server HTTP request sending, to avoid possible SSRF (#9079) by @mytharcher Reference: Environment variables
v2.0.36
Release date: 2026-04-10
🐛 Bug Fixes
- [client] fix subtable adds many-to-many field error (#9070) by @jiannx
- [flow-engine] Fixed the problem that many-to-one fields from external data sources cannot be added in the table block (#9068) by @jiannx
- [Notification manager] Optimize in-app notification sending performance in workflow scenarios (#9066) by @mytharcher
v2.0.35
Release date: 2026-04-09
🐛 Bug Fixes
- [client] Fixed an issue where the record pickup popup from a sub-table’s selection button could not correctly resolve parent item variable values. (#8996) by @gchust
- [Collection field: Code] Correct the UI interface of the code fields (#9061) by @2013xile
develop

v2.1.0-alpha.16
Release date: 2026-04-14
🚀 Improvements
-
[undefined]
-
[server] Improved swagger API docs of plugin manager (#9080) by @2013xile
🐛 Bug Fixes
- [AI employees] Fixed the issue where error messages were not displayed in the AI employee conversations (#9097) by @cgyrock
- [Access control] update acl swagger for mcp server (#9096) by @Andrew1989Y
v2.1.0-alpha.15
Release date: 2026-04-10
🎉 New Features
-
[Block: Tree] Add tree filter block (#9016) by @jiannx
-
[Auth: API keys] add
pm listandgenerate-api-keycommands (#9076) by @chenos -
[AI employees]
-
[Migration manager] support migration command by @chenos
-
[Email manager] gmail supports sending emails with aliases by @jiannx
🐛 Bug Fixes
-
[flow-engine] Fixed the problem that many-to-one fields from external data sources cannot be added in the table block (#9068) by @jiannx
-
[client]
- fix subtable adds many-to-many field error (#9070) by @jiannx
- Fixed an issue where the record pickup popup from a sub-table’s selection button could not correctly resolve parent item variable values. (#8996) by @gchust
- Fixed an issue where an incorrect unsaved changes confirmation message would appear for bulk edit action (#9054) by @gchust
- Fixed an issue where an incorrect secondary confirmation popup would appear when submitting the form after creating a record via a popup subtable. (#9035) by @gchust
- Fixed the issue where ctx.request could not override the Authorization header. (#8850) by @gchust
-
[data-source-manager] Fixed an issue where some field types were not updated correctly after syncing fields from the database (#9046) by @2013xile
-
[Notification manager] Optimize in-app notification sending performance in workflow scenarios (#9066) by @mytharcher
-
[Collection field: Code] Correct the UI interface of the code fields (#9061) by @2013xile
-
[Workflow: HTTP request node] Sanitized workflow request node results to avoid exposing request config, defaulted new nodes to return response data only, and added debug logging for failed requests. (#9024) by @mytharcher
-
[AI employees]
- Fixed the issue where abort AI employees reasonning would cause the service to crash (#9031) by @cgyrock
- Fix AI employee document upload failure under subpath access with APP_PUBLIC_PATH configured. (#9034) by @cgyrock
- Fixed the issue when using Deepseek or MiniMax models on dashscope (#9033) by @cgyrock