v0.5.0

• §11.4: the element now has overflow-x: clip, so a table wider than the element is cut off at its edge instead of drawing over the page beside it. A page can set overflow-x on the element, for example auto to scroll wide tables; the file's own style block can't.
• §11.4 adds a SHOULD: when the box that holds the table grows with it, renderers should also clip or scroll what doesn't fit in the space the page gives the table.
• §11.6: parse() stops with a §11.6 error past 1,000,000 cells (records × columns), before padding any record, so a short file with one long record can't build a huge table. MAX_CELLS is exported, parse(text, { maxCells }) takes another limit, and the element renders nothing and reports it. §11.6 now lists cell count among the limits a renderer may set.
• Appendix B: a monospace value with a backslash before a | is written as … with its content escaped, since a GFM table would end a code span's cell at that |.
• The skill says to import only stylesheets you trust (§11.3), and that a wide table is cut off unless the page sets cssv-table { overflow-x: auto; }.
• The README, llms.txt and the skill load the renderer from @0.5.

v0.4.0

• A style block can start with cssv: comments that give the file a title and a description, such as /* cssv:title Team budget / and / cssv:description ... */. They count only at the start of the style block, with nothing but white space and other comments before them, and change nothing in the table. Processors may show them, as plain text only, and every other cssv: name is reserved (§4.6).
• metadata(text) returns { title, description } from those comments, without parsing CSS.
• The complete example in §12 has a title and a description.
• The skill and llms.txt tell models to open every file with a title and a description.
• The README, llms.txt and the skill load the renderer from @0.4.

v0.3.0

• --cssv-key accepts col(n), the nth column counted from 1, whatever its name: for exports whose column names change, such as a header with the month in it, and for one of several columns that share a name. A quoted "col(2)" stays a name, and the host's key attribute takes names only (§9.1).
• parseKey() reads a --cssv-key value, and toHtml()'s key option also takes a column number.
• The README opens with an intro animation rendered from real tables.
• The README, llms.txt and the skill load the renderer from @0.3.

v0.2.1

No changes to the renderer or the processor.

• The skill's number table is corrected: in a comma-delimited file 1.200,50 is two fields, and 1.200 is the number 1.2. The skill explains how to convert values written as 1.234,50 and ends with a script that checks a file for common mistakes. It also covers src, update(), ready and errors.
• The README's install section pins @0.2, like every other link, and lists parseCssvValue.

v0.2.0

• update(text) shows a new CSSV text and returns ready. Relative URLs in it resolve against the last file loaded, or the page.
• A render patches the table on screen when the columns and @imports stay the same: changed cells get new classes and text, changed rules are swapped in place, and rows are added or removed where they changed, so inserting one row adds one .
• A full render keeps the shown table on screen until the next one is ready, instead of hiding the element while styles load (§8.3).
• The browser tests and the benchmark use an existing Chrome when CHROME_PATH is set.
• The README, llms.txt and the skill load the renderer from @0.2.

v0.1.1

0.1.0, the first release, was published without a tag. It had the CSSV v1 specification, the processor (src/core.js), the renderer, the conformance matrix, the README, the skill and llms.txt.

Changes since 0.1.0:

• The name is hyphenated, Comma-Separated Styled Values, as RFC 4180 names Comma-Separated Values. The npm description follows.
• Inline text in <script type="text/cssv"> can be indented like the markup around it: the renderer removes the first line's indentation from every line (Appendix C; inlineText() in core.js). An indented "---" used to be read as data, with no error.
• §7.5 and §11.3 say that key values are the one cell value copied into attributes, and that any stylesheet, including an imported one, can choose the key column unless the host sets it.
• The README shows how to restrict remote loads with a Content Security Policy.