SilverBullet 2.8.0 is here. The headliners this release are X-Ray, a new editor lens that lets you inspect indexed objects inline as you write (just run Editor: Toggle X-Ray), and a brand new built-in Journal library for journaling workflows. As usual, there's also a healthy pile of fixes as well.

Changes

• X-Ray: an editor lens (run Editor: Toggle X-Ray) to inspect indexed objects inline.
• New built-in Journal library.
• Runtime API: Expose objects (with filter) /.runtime/objects/* for external integrations and the CLI, see Runtime API.
• New SB_DISABLE_SERVICE_WORKER : server-side switch to disable the client service worker for all clients, this will disable sync (all loads and saves will go directly to the server) and disable any offline support.
• UX: now showing spinners instead of underlying (Lua) code in states where widgets aren't ready to render yet (e.g. before an initial index hasn't completed)
• Fix: indexed range for data blocks (and #tag data blocks) now points at the YAML content instead of the surrounding fence markers; multi-document blocks now compute per-doc ranges correctly.
• sb CLI changed how it encrypts secrets, so if you used token or password-based auth you need to re-add your space.
• Fix: indexed range for space-lua and space-style blocks now points at the inner code, not the ``` fences.
• Fix: Page Templates are now fixed (required specifying of suggestedName before), now also supports objects as frontmatter
• Removed: tapping the top bar (page name / action buttons area) no longer scrolls the editor to the top.
• Fix: page decoration prefixes now consistently appear in query-driven lists
• Fix: Safari/WebKit no longer renders block lua widget (queries, etc.) borders at the wrong position on first paint (previously required hovering or resizing the window to clean up).
• Fix: page navigation should now glitch less.
• Fix: browser back/forward now restores the scroll position you last had on each page.

Upgrading

• For docker-based install, pull the new image, stop the container and start a new one. For binary-based installs run silverbullet --upgrade and restart.
• After upgrading the server, make sure you reload all your SilverBullet tabs a few times, just to make sure the cache is flushed.

SilverBullet+

This release also coincides with the first "stable" release of SilverBullet+, which will follow the same release schedule.