v1.5.1
Release date: 2026-11-20
The release adds flip change history, components, connecting the flip mobile app to the installation server and new MCP server tools. The backend configuration parameters History.* and S3.Folders.ComponentsFolder are added.
New features
- The «History» panel on a flip: a log of created, changed and deleted objects with the «All», «Only mine», «Select users» and «Period» (7, 14 or 30 days) filters and restoring deleted objects with the «Restore» button. AI agent actions are marked with the «AI» label. The history is available to the flip creator, the space owner and space members with access to the flip; objects are restored by users with edit rights. Retention is set by the
History.*parameters of the backend configuration. - Components: the «Create component» command turns selected objects into a main component, whose linked instances are inserted on any flip of the space from the «Components» panel with the «Insert instance» button. Changes to the main component are applied to its instances; changes to an instance are sent with the «Push changes to main component» command and are accepted or rejected in the «Change request» card.
- The component card in the «Components» panel: «Editors» — users who can change the main component; «Variables»; «Discussion»; «History» with returning to a previous version with the «Restore» button; locking instances from editing («Lock instances?»). The «Components» panel with search and a tag filter is available to space members.
- Connecting the flip mobile app for iOS and Android to the installation server. The «Mobile app» section is added to the space profile (available to the space owner): the «Sign-in via mobile app» toggle, a QR code for connecting to the server («Share QR code»), the «Server display name» field and app download links. When sign-in is turned off, mobile app sessions are closed; changes to the setting and blocked sign-in attempts are recorded in the «Audit log».
- The «Changing answers» poll setting in the «Poll settings» menu: a participant changes their answer with the «Change answer» button while the poll is running.
- Table focus mode: the «Full screen» item in the table menu opens the table in full screen with a zoom selector; a link to this mode is copied with the «Copy link to focus mode» item. (frontend)
- New MCP server tools: flip history and restoring from it (
get_board_history,restore_from_history), starting and finishing a poll (start_poll,finish_poll), components (create_component,publish_component,update_component,search_components,get_component_history,get_component_discussion). Theadd_polltool accepts thechangeableVoteparameter. (mcp-server)
Improvements
- Flip lists: the full name in a tooltip when the name is truncated, opening a flip in a new tab with the middle mouse button or Ctrl/Cmd+click, sorting the list by column headers, filters by team and creator in search results. (frontend)
- Search by flip, folder, document and team names and by user name finds matches regardless of the Unicode form of characters, for example «й» as a single character or as the letter «и» with a separate breve mark. (backend)
- The «Verification certificate» field of the SAML settings accepts a certificate in DER format, as well as in Base64 with line breaks. (backend)
Fixes
- In the team list, a team whose owner has changed is shown once and with the current owner. (backend)
- When importing from Miro, images keep their group membership. (backend)
- Deleted element marks in Valkey are created with a limited retention period; previously, on on-premise installations they were stored without expiration. (backend)
- An image on the flip does not stay dimmed after loading. (frontend)
- «Search for objects on the board» finds objects added or changed after the search was opened; leading and trailing spaces in the query are ignored. (frontend)
- A table in a document does not extend beyond the document borders after the document is restored. (frontend)
- A table inserted into a document with the «/» → «Table» command is created with the same row height as a table on the flip. (frontend)
- In view and comment modes, clicking a document opened in full screen does not open the document menu. (frontend)
- When a voting area is selected, the flip toolbar is hidden. (frontend)
- The link button in a table cell is not covered by the cell background after the flip is reloaded. (frontend)
- In Safari, text with synthetic bold is wrapped the same way as in Chromium. (frontend)
Configuration changes
backend
History.EntriesLife— added, optional. Retention period of flip history entries; defaults to2160h. The value cannot be less thanHistory.TombstonesLife, otherwise backend does not start. Example:2160h. See backend configuration.History.TombstonesLife— added, optional. Retention period of copies of deleted objects used to restore an object from history; defaults to720h. Example:720h. See backend configuration.History.FeedDepth— added, optional. Depth of the «History» panel feed; defaults to720h, but not more thanHistory.EntriesLife. A value greater thanHistory.EntriesLifeis a backend startup error. Example:720h. See backend configuration.S3.Folders.ComponentsFolder— added, optional. Bucket prefix for component files; defaults tocomponents/at the same level asElementsFolder. Example:components/. See backend configuration.
Upgrade steps
- Check the mobile app sign-in setting: after the update, «Sign-in via mobile app» is turned on. If sign-in from the mobile app is not needed, turn it off in the «Mobile app» section of the space profile under the space owner account.
- Update mcp-server together with backend or after it: with an older backend version, the
start_pollandfinish_polltools are denied. - Do not interrupt the first backend start after the update. If the migration fails with the
index build on elements in progressorcomponent key index on elements missing or invalid after builderror, restart the backend container: the migration drops invalid indexes and builds them again.
Database migrations
On the first start, backend builds two indexes on the elements table (CREATE INDEX CONCURRENTLY). On large databases backend takes longer to start; writes to the table are not blocked while the indexes are built.