Upgrade / Upgrade to 0.6 and 0.7
Upgrade / upgrade-0-6
Upgrade to 0.6 and 0.7
What changed, what to run, and how to move cms_gaps before anything drops it.
On this page
warning
If you used 0.5 search gaps, copy cms_gaps into a table of your own before you change your schema. Removing cmsGaps from your Drizzle schema can make drizzle-kit generate a DROP TABLE.
New package name#
The package is now @mainsoft/agent-cms on npmjs.com. Remove the @mainsoft-2024 lines from .npmrc, then:
npm uninstall @mainsoft-2024/agent-cms
npm i @mainsoft/agent-cmsImport paths change their scope only: @mainsoft-2024/agent-cms/http becomes @mainsoft/agent-cms/http. Copied screens: run npx @mainsoft/agent-cms add --update.
Database#
npx @mainsoft/agent-cms migrate check
npx @mainsoft/agent-cms migrate apply0.6 adds columns and the cms_audit table. Until you run it, the CMS answers schema_outdated (503).
Code#
- Every collection needs
visibility: "public"or"internal"; internal ones needaccess.read. - Errors:
erroris now a fine code (conflict_version), the old value is inkind. updatetreatsfieldsas a JSON Merge Patch (nullremoves a key).- Gaps are gone from the library. Use
onSearchMissand your own table (see Search). - Peer
zodis^3.25or^4.
Moving cms_gaps#
- Create your own table (for example
app_search_misses). - Copy the rows with one
INSERT … SELECTand compare the counts. - Keep
cms_gapswhile you switch; agent-cms never reads, writes or drops it, anddoctoronly warns. - Collect new misses with
onSearchMiss. - Drop
cms_gapslast, when you no longer need it.
The full SQL, the Drizzle table and an onSearchMiss upsert are in UPGRADE-0.6.md.
0.7#
Nothing to change. mcp: { anonymous: "read" } is new and off by default.