twilight ventureswhat's new
Every product's newest note, latest first. Each note is dated by the day its version went live on its store. The three latest notes of each product sit on its own page. The changelog has every older note as well. The same notes are an Atom feed at /feed.xml.
JSONL Lens 2.0.0published 2026-10-27
With 2.0.0, records can be edited in JSONL Lens. Read-only stays the default; "Edit" in the toolbar turns it on, and the file is untouched until you click "Save… (Pro)". While Edit is on, the detail pane takes a record's JSON; "Stage" (or Ctrl+Enter) keeps the change once it reads as one JSON value, and text that does not is left unstaged with the parser's position shown. "Add record" adds an empty record after the last line, to fill in the same pane. "Review" shows each staged record next to the line the file holds now. The save rewrites only those lines, in place, and every other byte stays as it was. The IDE's Local History keeps the version before the save, "Keep a copy of the file before saving" leaves a copy beside the file, and "Undo last save… (Pro)" takes a save of changed records back until the file is closed or reloaded; a save that added records cannot be undone, and the preview says so before Save. A compressed file keeps Edit off. A record past 16 MB, and a file that changed on disk since it was opened, are not written, and the reason is shown. Edit mode, staging and "Review" are free; saving is Pro.
XLSX Lens 1.7.0published 2026-10-27
With 1.7.0, cells can be edited in XLSX Lens. Read-only stays the default; "Edit" in the toolbar turns it on, and the workbook is untouched until you click "Save… (Pro)". While Edit is on, a double-click or F2 opens a cell, Ctrl+V stages a block copied from a spreadsheet, "Add row" appends a row at the end of the sheet, and "Set column for visible rows…" puts one value on every row the loaded page shows. "Review" shows each change next to what the file holds now. The save writes the file in place: the IDE's Local History keeps the version before it, "Keep a copy of the file before saving" leaves a copy beside the workbook, and "Undo last save… (Pro)" takes the save back until the file is closed or reloaded. A formula cell, a cell inside a merged range and a protected sheet cannot be edited and say why; a cell that feeds a formula can, and Excel recomputes the formula when the workbook opens. Edit mode, "Review", paste, "Add row" and "Set column for visible rows…" are free; saving is Pro.
Notebook Lens 1.3.1published 2026-10-27
The 1.3.0 cut, uploaded a second time; nothing in the plugin changed.
DuckDB Lens 1.4.1published 2026-10-27
The description's first paragraph now reads read-only by default, and says the file is never written until you say so. Everything 1.4.0 added stands; no code changed.
JSONL Lens for VS Code 0.6.0published 2026-10-27
records can now be edited in the viewer. double-click a record, or any cell of it, and it opens in the pane beside the grid as its JSON text; change it and press Stage, or Ctrl+Enter. the row then shows a colored edge, and a bar above the status line counts what is not saved yet ("Not saved yet: 2 records changed, 1 added") with Undo, Discard and Save. Add record opens an empty record that goes after the last one. Save in the bar, or the editor's own Save (Ctrl+S), writes the changes into the file in place: only the text of the records you changed is written again, and every other line, the line endings, the blank lines and a byte order mark stay as they were. until then the tab shows the unsaved mark, and Undo or Ctrl+Z takes the last change back. staging and the bar are free; the save is a Lens Pro feature, which the trial includes, and without it the prompt reads "Saving an edit is a Lens Pro feature. Opening a record, staging it, Undo and the bar that counts the unsaved records stay free." and your changes stay staged. a text that is not one JSON value is not staged, and the pane says where reading it stopped; a text with a line break is not staged either, since a record is one line. nothing is written when the file changed on disk after you opened it: the save is refused with "This file changed since you opened it; revert and edit again." a gzipped file, or one over 512 MB, still opens for reading only.
Data Lens: Excel, Log, CSV Viewer & Editor for Confluence 3.2.0published 2026-10-27
A CSV or TSV cell can now be edited on the page: double-click, type, press Enter, and the change waits in a list with Undo and Discard until you click Apply. A confirmation lists every change, then the file is saved as a new version; the earlier versions stay in the history. The Versions button opens any earlier version, and Revert saves it back as a new version. If the file changed since you opened it, the save is refused. The update asks admins for one new permission, writing attachments, and readers may see an Allow access prompt once.
JSON attachments up to 50 MB open: an array, or an object holding one, becomes the table; anything else opens in the detail pane.
The macro and its settings page appear in the language of each reader's Atlassian profile: German, French, Spanish, Brazilian Portuguese, Japanese, Simplified Chinese, Korean and Hungarian, with English for any other language. File names, formats and the data stay as they are; the Rovo agent still answers in English.
Data Lens: Excel, Log, CSV Viewer & Editor for Jira 3.2.0published 2026-10-27
A CSV or TSV cell can now be edited on the work item: double-click, type, press Enter, and the change waits in a list with Undo and Discard until you click Apply. A confirmation lists every change, then the file is saved as a new attachment named with the date, and a comment on the work item names the change. If the original changed since you opened it, the save is refused. The update asks admins for new permissions: writing attachments and comments, and the reads Jira pairs with them. The original attachment stays untouched beside the new one, and readers may see an Allow access prompt once.
JSON attachments up to 50 MB open: an array, or an object holding one, becomes the table; anything else opens in the detail pane.
Also in this version: a log of up to 96 MB is fetched once, Excel Long Dates and Times follow the language of your Atlassian profile, a case-insensitive Find matches Cyrillic and Greek, and a damaged workbook is refused with a reason instead of opening empty.
Heap Dump Lens 1.4.13published 2026-10-25
A thread dump that jcmd Thread.dump_to_file writes on JDK 25 in its text form now opens with its threads. JDK 25 puts each thread's state on the line that names it, a line the viewer up to 1.4.12 did not expect, so it read no thread from such a file and the table said "No jstack, Thread.print or Thread.dump_to_file threads in this dump". Each thread comes in with its frames and lock lines, and its state shows in the State column.
Parquet Lens 1.9.11published 2026-10-22
Four kinds of damaged or changing file now get a message that says what is wrong. An Arrow or Feather file that another program cuts short while its rows are on screen says the file changed on disk and offers Reload. An Arrow schema nested deeper than 64 levels is refused at open as nested too deep, where a stack overflow raised the error. An Avro file whose block record count is damaged is refused with the block named, where another block's records showed at the wrong row numbers. A gzip or zlib TFRecord file that inflates more than 100 times past 128 MB is refused as a decompression bomb, with the advice to decompress it outside the IDE, where a 1.6 MB file of zeros wrote 1 GB into the temp folder.
Log Lens 1.9.12published 2026-10-17
In a plain-text log, a line without a time stamp that opens with a level word more severe than the stamped line above it counts under its own level again, in the level chips, in follow and in Log Statistics. 1.9.11 counted such a line under the stamped line, so a Go panic printed after a line from Go's log package (a time stamp and no level) counted as OTHER and was missing from the FATAL chip, and a JVM WARNING line or an "ERR!" line from a package manager after an INFO line was missing from WARN and ERROR. A level word further along a line changes nothing: the lines after the panic, an exception message that names FATAL in its text and every stack trace line still count under the stamped line above them.
SQLite Lens 1.7.7published 2026-10-17
A whole-table sort (Pro) with "Order text by bytes" now reads the rows in an index's order when the table has an index on that one column, under the BINARY collation, neither partial nor on an expression: sorted ascending, the first page of a large table comes at once, where every such sort read the whole table first (0.1 ms against about 4 seconds for the first 100 of 1,000,000 rows). Byte order stays the bytes on a column declared NOCASE, RTRIM or with a collation only its app registers, as Room's LOCALIZED, and that column's own index is not used for it. Two texts that differ only past their first 4,097 characters now sort by the whole value. While a sort reads rows before its first page, the status line reads "sorting by ts (whole table)…" and the IDE's task line says what it is sorting and what Stop will do. "Apply the WAL and turn Edit on", clicked again once the app that held the database has quit, now says "Nothing was waiting in the WAL any more, so nothing was written." under "Nothing to apply to events.db" instead of reporting an apply. When applying the WAL stops part way, on a full disk or after a failed write, the Edit strip says "The frames are still in the -wal, and any SQLite that opens the file read-write finishes the job." and the tab shows the database's rows from a recovered copy, where it showed "database disk image is malformed". Before it starts, the apply checks that the disk can hold the frames, and the copy when "Keep a copy of the file before applying" is ticked.
Parquet Lens for VS Code 0.6.21published 2026-10-17
"Copy rows as CSV" (free) now puts an apostrophe in front of a cell whose first character is =, +, - or @ when the cell is not itself a number, so =SUM(A1) arrives as text while a signed number arrives as the number. the CSV export (Pro) writes its cells the same way; commas, quotes and line breaks are quoted as before. a hard link of the open file is refused as a destination with the words "Export destination is the source file under another name (a hard link, or the same path in another case)", where the refusal read "Export destination is the source file".
Log Lens for VS Code 0.2.15published 2026-10-17
a CSV export (Pro) now writes a leading apostrophe into any field that starts with =, +, - or @, or with a tab or a carriage return, and is not a plain number: the message, the level, the time or a named field alike. =cmd|x is written as text; a field that is only -1 stays the number -1. the export also refuses a hard link of the log as its destination, with the sentence "Export destination is the source file under another name (a hard link, or the same path in another case)"; the log's own path and a symbolic link to it were refused before, and a write through a hard link would have emptied the log while it was being read.