Skip to content

chore: version packages - #1503

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: version packages#1503
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@lostgradient/chat@0.14.0

Minor Changes

  • #1489 398237e Thanks @stevekinney! - Extend ChatStreamEvent additively to carry Operative's full stream and run event vocabulary (stream:*, tool.*, run.*) plus a wireVersion / sequence wire envelope. The three original members (text, tool_call, tool_result) keep their exact current shapes and decode unchanged, with or without the new envelope fields.

Patch Changes

  • #1488 9343fcd Thanks @stevekinney! - Raise the conversationalist dependency floor to ^1.1.0, matching what @lostgradient/operative requires, so a host running Chat alongside Operative resolves a single ConversationHistory implementation instead of two divergent nested copies.

  • #1493 dae3c6e Thanks @stevekinney! - Cap the grouped tool-call transcript row (ToolCallTimeline's .chat-tool-call-timeline) to the same shared readability max-width every other row respects, via the new --cinder-chat-message-max-width token. Previously this row — the one carrying the widest content in the transcript, serialized JSON arguments and results — had no inline-size constraint of its own and stretched to the full timeline width on wide viewports. Also fix a grid track sizing issue that let an expanded tool-call group's long, unbroken payload blow out past that cap instead of scrolling within its own code block.

  • #1507 8fee818 Thanks @stevekinney! - Keep each component's stylesheet in a consumer's client bundle. The package listed only **/*.css under sideEffects, so a Rolldown-based bundler (Vite 8) treated the component barrels that import those stylesheets as side-effect-free re-export modules and skipped them entirely, dropping the chat.css sidecar from production client output while the Vite dev server still served it. The barrels (src/lib/components/*/index.ts and dist/components/*/index.js) are now declared side-effectful too, using the same bare relative form as the sibling packages so every bundler matches them.

  • #1492 78195ad Thanks @stevekinney! - Fix visually-hidden status announcers rendering as ordinary visible text. Chat marked screen-reader-only content with the bare sr-only class, which had no CSS rule reaching most of the elements that used it — most visibly, a stray unstyled "Action required" line stacking above the intended tool-status chip. Every visually-hidden element now uses cinder-sr-only, the design system's utility (already required via @lostgradient/cinder/styles), and a guard script fails the build if a bare sr-only class reappears.

  • Updated dependencies [ed0dae6, 2bfdd13, 90b421f, 0b7c0f2, 2a5991f, c7e34f0, ff39cb2, 80221ef]:

    • @lostgradient/markdown@0.5.0
    • @lostgradient/cinder@0.26.0

@lostgradient/cinder@0.26.0

Minor Changes

  • #1502 90b421f Thanks @stevekinney! - Input keeps its native element when a leading or trailing addon appears or disappears. The control wrapper is now always rendered — .cinder-input-group with addons, a boxless .cinder-input-host (display: contents) without — so the <input> has one stable position in the tree instead of moving between template arms, and focus, the selection range, and IME composition survive the toggle. Unadorned inputs lay out exactly as before, and the host carries data-cinder-full-width so ancestors that detect a full-width control by direct child keep matching.

    DOM contract change for consumers styling the native control: an unadorned .cinder-input is no longer a direct child of its frame or of the element that composes it. Descendant selectors (.your-row .cinder-input) still match; a direct-child selector (.your-row > .cinder-input) must become .your-row > .cinder-input-host > .cinder-input. TimeField's own control-row sizing was the one in-repo case and is updated.

  • #1501 2a5991f Thanks @stevekinney! - Fix StatisticGroup's column collapse and row-end dividers. The group's @container rules queried the element that declared the container, so a standalone group never collapsed at the documented 30rem and 18rem thresholds. The public root (.cinder-statistic-group, which receives class, style, and every other prop) is now the query container, and the cells live in an inner .cinder-statistic-group__grid; a consumer that constrains the group's inline size constrains exactly what collapses, and a nested group queries its own width. The default variant's row-end divider suppression was also inert — the generic enabler out-ranked every nth-child suppressor by specificity — so every group that wrapped to a second row drew a divider at the end of each row. Divider rules are now enumerated per column count at uniform specificity and follow the collapse thresholds, so they describe the grid that actually renders. Note that the query measures the root's content box, so for the padded default variant the thresholds apply to the width the cells share.

    DOM contract change for consumers styling the group: the grid moved from .cinder-statistic-group to an inner .cinder-statistic-group__grid, which is now the documented layout hook. Consumer class and style still land on .cinder-statistic-group, but a grid-template-columns or gap override written against the root no longer reaches the cells; target .cinder-statistic-group__grid instead, or keep using --cinder-statistic-group-gap on the root, which the grid still reads. .cinder-statistic cells are no longer direct children of .cinder-statistic-group: descendant selectors still match; a direct-child selector (.cinder-statistic-group > .cinder-statistic) must become .cinder-statistic-group > .cinder-statistic-group__grid > .cinder-statistic.

  • #1496 c7e34f0 Thanks @stevekinney! - VirtualList: add dynamicSize for measured, variable-height rows, and a typed ref handle.

    dynamicSize opts a list into measuring each rendered row with ResizeObserver and caching the
    result, using itemHeight as the initial estimate for rows that have not been measured yet. When a
    measurement differs from the estimate, the scroll offset is corrected before paint so the viewport
    does not visibly jump. The fixed-height path remains the default and is untouched: with dynamicSize
    off, no row is measured, no size is cached, and no scroll correction runs. (The component observes
    its own scroll container to track viewport size in both modes, as it always has.)

    bind:ref now exposes a typed VirtualListRef with scrollToIndex(index, options), which accounts
    for the measured sizes of every row before the target and accepts align and behavior options.

  • #1511 ff39cb2 Thanks @stevekinney! - VirtualList: add horizontal for inline-axis virtualization, with right-to-left support.

    horizontal scrolls and lays rows out along the inline axis. itemHeight and height are
    reinterpreted rather than renamed — itemHeight becomes each item's width, height becomes the
    container's inline-size — and --cinder-virtual-list-height keeps its name while switching to drive
    inline-size, so an existing theme override survives turning the prop on.

    Right-to-left is handled rather than assumed. The writing direction is resolved from the container's
    computed style, and the RTL scrollLeft convention is feature-detected once per document: browsers
    disagree on both the sign and the origin of scrollLeft in a right-to-left container, and current
    browsers use the negative convention that older ones did not.

  • #1512 80221ef Thanks @stevekinney! - VirtualList: add reverse for chat transcripts, and onEndReached/onStartReached
    for bi-directional infinite scroll.

    reverse opens the list at its newest item and returns there on every append,
    regardless of where the reader has scrolled — distinct from stickToBottom, which
    pins only when the reader is already at the bottom. Items keep their natural order;
    reverse names the anchoring, not the ordering. Prepending older history anchors to
    the row the reader was on instead of moving them.

    onEndReached and onStartReached fire as the reader comes within overscan items
    of either edge. Each fires once per approach and re-arms when the item count changes,
    so appending in response allows the next page while a source that returns nothing
    does not spin.

    Also repairs two scroll reads left on the block axis by the horizontal work: the
    dynamic re-pin comparison, and the settle loop in scrollToIndex, which saw no
    movement on a horizontal list and so skipped its settle pass entirely.

Patch Changes

  • #1513 2bfdd13 Thanks @stevekinney! - Share one declaration of the Input's invalid-hover border between the input, its host wrapper, and the group. The three surfaces that can paint that edge each derived it separately, so they could drift apart, and the duplication pushed the file past its raw-color allowance.

  • #1506 0b7c0f2 Thanks @stevekinney! - ShareCard renders its value field from a single Input call site. Previously the icon-only and labelSnippet layouts were two separate Input instances, so a parent that reactively changed actions across that boundary tore the field down and dropped the user's focus and selection. Now the actions move between the trailing addon and the sibling row as a prop update on the same element, and focus and the selection range survive.

  • Updated dependencies [ed0dae6]:

    • @lostgradient/markdown@0.5.0

@lostgradient/editor@0.14.0

Minor Changes

Patch Changes

  • #1508 67fd167 Thanks @stevekinney! - Stop the review editor's selection popover from re-opening over text whose comment was just submitted. Submitting hands focus back to the editor, ProseMirror re-writes its stored, still non-collapsed selection into the DOM, and that selectionchange used to re-open the popover. The editor now holds the submitted range until a pointer or key inside it starts a new selection.

  • Updated dependencies [ed0dae6, 2bfdd13, 90b421f, 0b7c0f2, 2a5991f, c7e34f0, ff39cb2, 80221ef]:

    • @lostgradient/markdown@0.5.0
    • @lostgradient/cinder@0.26.0

@lostgradient/markdown@0.5.0

Minor Changes

  • #1521 ed0dae6 Thanks @stevekinney! - Export BUNDLED_LANGUAGE_LOADERS, the curated per-language dynamic import map behind the markdown pipeline's Shiki highlighter.

    It was already the shape this package uses to stay off shiki/langs — the default shiki entry resolves to bundle-full.mjs, which statically references all 253 bundled grammars, so a bundler ships every one of them (~10 MB) no matter which languages a document actually contains. Exporting the map lets a second highlighting surface be built from the same curated set instead of reaching for the full registry, with one list to maintain rather than two that drift.

    Additive: no existing export changes shape, and the map remains exhaustive over BUNDLED_LANGUAGES by its Record<BundledLanguage, …> type.

@lostgradient/cinder-mcp@0.1.16

Patch Changes

@cinder/chat-room-lab@0.0.5

Patch Changes

@vercel

vercel Bot commented Sep 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
cinder-playground Ignored Ignored Sep 10, 2026 2:08am UTC

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 14 times, most recently from 6bce680 to 1dd58ff Compare September 8, 2026 19:10
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 6 times, most recently from a38b2ec to 795f50d Compare September 9, 2026 22:39
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 795f50d to dfc3890 Compare September 10, 2026 02:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants