v2026.10.2
このコンテンツはまだ日本語訳がありません。
Released 2026-10-11.
Features
Section titled “Features”-
The CMS is generally available. The CMS is now on for every workspace, with nothing to turn on first, and sits in the sidebar next to Forms. With the workspace-wide switch gone, you stop a site one at a time — unpublish it or revoke its API keys. OGP image generation is still experimental.
-
A CMS entry screen made for writing.
- Write the body the way it will read. Rich text fields get a visual editor with a toolbar that is always there, and a row under it for a link’s address or an image’s alt text. What is saved is still Markdown, so the published JSON, the read API and exports are unchanged, and a Visual / Markdown switch in the top-right corner flips between the two at any time. A body that uses something the visual editor can’t write back exactly — tables, HTML, task lists, footnotes, line breaks inside a paragraph — opens as Markdown, so opening an entry and saving it never changes it.
- The main fields come first. In a content type with a rich text body, the first text field becomes a large headline with the body beneath it, and every other field moves to a column on the right. Slug and scheduled publishing are grouped under Publishing, the save and publish buttons stay pinned to the top along with their result, and when publishing is stopped by a validation error the screen scrolls to the field.
- Choose the main fields per content type. For types led by something other than text — a portfolio, a gallery — pick which fields lead the entry screen, and in what order, under Main fields on the entry screen in the content type’s settings. Images in a main field are shown large, and several images can be reordered.
- Unsaved changes are protected. Closing the tab, reloading, or following a link inside the entry screen asks before discarding your edits, and adding a language saves the original entry first.
- Field API IDs are shown only while integration mode is on.
-
Minion DB Studio: table databases that live on your minion. A new official app for data that has outgrown a spreadsheet. Create a database, add tables and typed columns — choices, required fields, references to other tables — and work in a grid that stays fast on large tables: edit cells in place, filter, sort, pick the columns you see, and keep the result as a saved view. Rows can carry attachments, with image thumbnails in the grid.
- Bring data in and take it out. Import CSV (Shift_JIS included) or an Excel sheet through a preview where you confirm the header row and column types, into a new table or an existing one, with a report of the rows that didn’t fit. Export to CSV or Excel, optionally leaving out the columns you marked as personal data.
- Changes you can undo and trace. A schema change that could lose data shows what it will affect before you apply it, and a snapshot is taken first. Snapshots are also taken daily and on demand, and any of them can be downloaded or restored as a new database. A change log records who — a person or a minion — changed what, and when.
- Works with Drive. Save a link to the database, a full copy
(
.mi-db.zip) or an exported table to Drive, and open them from Drive again. - Your minion can use it too. Everything the screen does is available to the minion through the same operations, so you can ask it to build a database, load a file into it, or keep it up to date.
Experimental, like the other official apps.
-
Edit a note together, live. Several people can now work in the same note at once — meeting minutes, for example — seeing each other’s cursors, with everything typed appearing for everyone as it happens. When a minion updates a note you have open, its changes arrive without a reload: the changed text is highlighted for a moment with the minion’s name, and whatever you were typing in the meantime stays. Experimental — turn it on under the workspace’s experimental features.
-
Profile pictures on the board. A ticket’s assignee is shown with their profile picture, or their initials when they haven’t set one, on cards, in planning and the table, in sprint history and in filters.
Improvements
Section titled “Improvements”-
One storage allowance for the whole workspace. Drive and the CMS used to have separate quotas. There is now a single allowance per workspace — 2 GB on Free, 20 GB on Starter, 100 GB on Team, 400 GB on Business and 2 TB on Enterprise — shared by Drive files, CMS media, note images and document assets. It equals the two old quotas added together. Note images and document assets, which could previously be added past the limit, now stop at it too, and a note image that doesn’t fit says so instead of just failing. The storage meter in Drive breaks usage down by where it comes from. The largest single file is the same on every plan: 100 MB in Drive and 25 MB for CMS media.
-
Plan limits are shown where you pick and manage a plan. The pricing page lists members, CMS sites, storage and minions for each plan, and the billing page shows each workspace’s CMS sites and storage against its limits. The Plans page explains how each is counted and what keeps working when a limit is reached.
-
Downgrades check CMS sites and total storage. Moving to a smaller plan now checks the number of CMS sites and the workspace’s whole storage use, not just Drive, and the billing page says which of them is in the way.
-
Dropdowns look and work the same everywhere. Every dropdown in the app now uses one shared control instead of the browser’s own, so they look alike on every browser and operating system, work fully from the keyboard, and no longer get cut off inside drawers and tables. In a ticket’s details, the assignee dropdown shows profile pictures.
-
Minions edit a note in place. A minion can now replace a passage or append to a note instead of rewriting the whole text, so an edit it makes no longer undoes what someone typed while it was working.
-
Only current project members can be assigned a ticket. People removed from a project stayed in the assignee list for as long as they were in the workspace. Someone who has left but still holds a ticket is still shown as its assignee, marked “(not a member)” — tickets held by a removed minion used to look unassigned. A minion removed from a project no longer picks up that project’s tickets on its own.
-
CMS API rate limits are counted per site, as documented. The limit was counted per API key, so every extra key raised it, and reads and writes shared one counter — 60 reads in a minute left no room for a write. Reads (300 per minute) and writes (60 per minute) are now counted separately for each site, and requests with invalid keys are limited by where they come from.
-
Sites with a lot of media can be duplicated. Duplicating a CMS site compared the combined size of its media with the limit for a single file, so larger sites failed with a “file too large” error.
Includes @geekbeer/minion 5.21.4 and DB Studio 0.5.1. Deck Studio 0.12.0,
Image Studio 0.7.0, Video Studio 0.36.6 and Media Home 0.24.3 are unchanged.