[{"data":1,"prerenderedAt":149},["ShallowReactive",2],{"changelog-releases":3},{"releases":4,"hasMore":146,"nextOffset":147,"total":148},[5,48,80,114],{"slug":6,"title":7,"date":8,"lede":9,"tags":10,"body":12},"2026-03-02-batch-export","Batch export for project files","2026-03-02","Export multiple project files at once instead of downloading them one by one.",[11],"Feature",{"type":13,"value":14},"minimark",[15,19,23,26,42,45],[16,17,18],"p",{},"Placeholder body copy: exporting used to mean opening each file, clicking export, waiting, and repeating. For anyone working across a large project that added up fast, especially right before a deadline when every extra click felt like friction.",[20,21,22],"h2",{},"How it works",[16,24,25],{},"Select any number of files from the project list, choose a format, and the export runs as a single background job. You get a notification when the archive is ready instead of staring at a progress bar.",[27,28,29,33,36,39],"ul",{},[30,31,32],"li",{},"Select any number of files from the project list",[30,34,35],{},"Export as a single .zip archive, or as individual files",[30,37,38],{},"Large exports run in the background so you can keep working",[30,40,41],{},"A notification lets you know when the archive is ready to download",[20,43,44],{},"What's next",[16,46,47],{},"Placeholder body copy: scheduled\u002Frecurring exports and direct export to connected cloud storage are being explored for a future release.",{"slug":49,"title":50,"date":51,"lede":52,"tags":53,"body":55},"2026-02-18-faster-search","Faster search across large projects","2026-02-18","Search results now return noticeably faster on projects with thousands of items.",[54],"Improvement",{"type":13,"value":56},[57,60,63,66,77],[16,58,59],{},"Placeholder body copy: as projects grow past a few thousand items, search had started to lag noticeably, sometimes taking a couple of seconds to return results. This release rebuilds how the search index is stored and queried.",[20,61,62],{},"What changed",[16,64,65],{},"The underlying index now updates incrementally instead of being rebuilt from scratch on every change, and queries run against a more compact in-memory structure.",[27,67,68,71,74],{},[30,69,70],{},"Typical search response time dropped by roughly 70% on large projects",[30,72,73],{},"Search-as-you-type feels noticeably smoother, even on slower connections",[30,75,76],{},"Indexing now happens incrementally instead of rebuilding from scratch",[16,78,79],{},"Placeholder body copy: smaller projects should feel about the same as before, since the difference is most noticeable once you cross a few thousand indexed items.",{"slug":81,"title":82,"date":83,"lede":84,"tags":85,"body":86},"2026-02-05-comment-threads","Threaded comments","2026-02-05","Replies now nest under the original comment instead of appearing as a flat list.",[11],{"type":13,"value":87},[88,91,94,97,108,111],[16,89,90],{},"Placeholder body copy: comments used to appear as one long flat list in the order they were posted, which made it hard to follow a back-and-forth once a discussion had more than a few replies.",[20,92,93],{},"Threaded replies",[16,95,96],{},"Replying to a comment now nests that reply directly underneath it, so related messages stay grouped together instead of getting mixed in with unrelated ones.",[27,98,99,102,105],{},[30,100,101],{},"Reply directly to any comment to start a thread",[30,103,104],{},"Collapse a thread to tidy up a busy discussion",[30,106,107],{},"Jump straight to a thread from a notification",[20,109,110],{},"Migrating existing comments",[16,112,113],{},"Placeholder body copy: comments posted before this release are shown as a flat list at the top of the thread view, since there was no reply relationship recorded for them originally.",{"slug":115,"title":116,"date":117,"lede":118,"tags":119,"body":121},"2026-01-27-upload-retry-fix","Fixed a bug where large uploads could silently fail","2026-01-27","Uploads over 200MB no longer fail without an error message.",[120],"Fix",{"type":13,"value":122},[123,126,129,132,143],[16,124,125],{},"Placeholder body copy: on a slow or unstable connection, uploads over roughly 200MB could fail partway through without showing any error — the progress bar would just stop moving, leaving no clear next step.",[20,127,128],{},"Root cause",[16,130,131],{},"The uploader wasn't retrying failed chunks, and a single dropped chunk silently stopped the whole upload instead of surfacing an error.",[27,133,134,137,140],{},[30,135,136],{},"Failed chunks are now retried automatically, up to three times",[30,138,139],{},"A clear error message appears if an upload can't complete",[30,141,142],{},"You can resume an interrupted upload instead of starting over",[16,144,145],{},"Placeholder body copy: thanks to everyone who reported this one with enough detail to reproduce it reliably — that made it much faster to track down.",true,4,9,1792832836846]