{
  "id": 9693679,
  "title": "What a NocoBase upgrade actually changes",
  "url": "https://urgent.news/2026/09/25/what-a-nocobase-upgrade-actually-changes",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-25T03:29:32.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/stale_orbit/what-a-nocobase-upgrade-actually-changes-8ao"
  },
  "original_language": "en",
  "account": "NocoBase 2.1.39 to 2.2.14 upgrade resulted in a 4-table structure with minor changes. The table counts increased from 100 to 104, and columns rose from 855 to 899. Two columns were added to existing tables, and two additional tables were created specifically for AI usage events and user workflow task stats. No tables or columns were dropped. The upgrade also introduced two new pages in the admin UI that are stored in a different location than expected. Despite these changes, existing pages rendered correctly, and the UI stored them elsewhere. The upgrade process was straightforward, with no dropped elements or significant impacts on existing workflows.",
  "summary": "NocoBase ships fast. Between September 5th and 11th it published six patches. The changelog tells you what the team changed. It does not tell you what will happen to your database, your screens, your workflows. Someone raised the same concern on the official forum, in Chinese ( t/14099 ). In my translation, the gist is: I'm on V2.1.30 and don't dare move to V2.2.X, because I don't know what the…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}