Skip to content

mikanBox Cloud v0.9.0

Choose a tag to compare

@yoshihik0 yoshihik0 released this 09 Nov 12:49
· 28 commits to split-prototype since this release

mikanBox Cloud 0.9.0 remains a development edition. It follows mikanBox PHP 2.19.0.

  • Operation basics. The browser's alert, confirm and prompt are gone from the admin screen (a test fails if one returns). Results go to the toast at the bottom right; confirmations are asked in the screen.
  • No reload. Saving and deleting pages and components, memo, site settings, update source, devices and users, publishing, and choosing or adding a category run in the current screen. A new page or component becomes an existing editor after its first save.
  • Opening and closing editors. Page and design editors grow and shrink in, scroll to the top of the editor when opened and back to the edited row when closed, keep the filters, and ask in the screen about unsaved changes.
  • Preview shows the content being edited (unsaved changes and new pages included). It is not saved; the display stays isolated. The edited content is kept for 30 minutes (at most four per user, readable only by that user), in a new D1 table (migration 0018, applied by the update workflow).
  • MCP. New read-only preview_page (an ID alone previews the saved page; fields preview unsaved content, also for a new ID). get_site_info reports version; the connection guidance says to re-read the tool list when it changes; get_ai_context ends with a built-in output-formats document.
  • Full reloads remain only where the screen's premise changes: language change, restoring a backup, switching media storage (and cancelling its migration), restoring D1 to a time, stopping your own device, saving the connection settings, and file downloads. They are listed in the manuals.

After updating, check: open and close a page editor (no reload, back to the edited row), delete a page (an in-screen confirmation, a message at the bottom right), change the editor text without saving and press Preview, and confirm that no browser dialog appears anywhere. Publishing again is only needed if you have not published since 0.8.1 or later.

Validation: TypeScript checks and all 273 Cloud tests pass. Open/close, delete, in-place save, unsaved preview and the design editor were also driven in headless Chrome against a local dev server (no reload, no browser dialogs). Not yet checked on a real Cloudflare deployment.