Skip to content

Candor 6.1.2

Choose a tag to compare

@arunk3 arunk3 released this 15 Nov 20:47
· 2 commits to main since this release

Released 2026-11-15.

With CLI 4.2.0 and @candor-ui/react 6.1.2: the registry serves only the current release, 6.0's codemods and the
Upgrading to 6.0 page are removed, and nested lists in model text are drawn nested.

CLI 4.2.0

  • update, add and migrate work with Candor 6.1 and later. 6.1 is the first release CLI 4 installs with a copy
    of each file in .candor/base/, which is what update merges against now that the registry serves only the
    current release. On a project before 6.1 they change nothing and say how to move on: commit, delete
    candor-lock.json, run the codemods of the releases you crossed on your own code (with no lockfile, each runs all
    of its release's), then npx candor-ui@4 add <your items> --overwrite and take your edits back from git. An item
    6.1 removed can't be added; Upgrading to 6.1 says what replaced it.
  • On a project on 6.1 or later but behind the current release, no command stops on an earlier version the registry
    no longer serves. update merges against .candor/base/, and for an item without a usable copy stops before
    changing anything and names git checkout -- .candor/base or npx candor-ui@4 add <item> --latest --overwrite.
    add names update, or --latest. info shows the current page and says so. verify --remote checks the items
    at the current release and names the others as not checked. list --installed, theme check, add --dry-run's
    preview and migrate's list of new strings use .candor/base/ where they can, and otherwise say why they can't
    compare.
  • migrate no longer has 6.0's codemods: data-types, props and headings, and 6.0's rows of strings-keys.
    npx candor-ui@4.1 migrate 6.0.0 runs them. 6.1's (items, strings-keys, tokens) stay.
  • mcp and doctor no longer mention item_changes, which the docs server no longer has.

Registry and site

  • The registry serves only the current release. /r/versions.json lists it; /r/v/<another version>/… answers 410
    with a line naming npx candor-ui@4 update, which merges against your project's .candor/base/ and needs no
    earlier version. If you install with shadcn from a versioned URL, use the current one.
  • The docs MCP server has twelve tools: item_changes is gone, and a page asked for at another version is the
    current one, which it says.
  • Upgrading to 6.0 is gone: /upgrading-to-6 and its .md redirect to 6.0.0's section of this changelog. Upgrading to
    6.1 stays as the list of 6.1's changes and their codemods.
  • The docs no longer have a version list: only the current release's are published.

@candor-ui/react 6.1.2

Only these free items change.

  • Nested lists in model text (safe-markdown, message-content): markdownBlocks reads an item indented two
    columns or more past the item above it as nested in that item, ordered and unordered in each other, to four levels;
    an item deeper than that is one more item of the fourth level, with its text kept. A tab counts as four columns. An
    indented line that isn't an item continues its item, and after a blank line is a paragraph inside it. A list in a
    quote is read as a list, and a quote whose lines include a list is split into paragraphs around it. Before 6.1.2 each of these was a flat item, or a paragraph after the list. MessageContent
    draws what is under an item inside it, with hollow markers on a nested unordered list, and copies it as lines
    indented by its marker's width a level. The Claude Agent SDK adapter places a citation after the deepest last item.
    While a reply streams, an item is drawn at its own level from its marker on.
  • A list block gains nested (what sits under each item) and a quote block lists (which of its paragraphs is a
    list); both are left out when there is nothing to put in them, so a flat list's block and markup are as before. If
    you draw blocks yourself, draw nested inside each item; left undrawn, the nested items are missing, not flattened.
  • Thread lands a tall new message at its start (thread): with landNew="start", a new message taller than the
    view, whether it arrives whole or grows there while it streams, stops the view at its start and the thread stops
    following, so the opening of a long reply stays in view and Jump to latest shows; the reader's own message
    (data-role="user") and anything shorter than the view are followed to the end. A reply that takes the place of a
    placeholder row lands as a new message does. If you draw the reader's messages yourself rather than with Message,
    mark them data-role="user", or they can land too. The default, "end", follows as before. The newest message in a thread now carries data-newest, so you can find it without relying on Message's
    data-slot and data-role.

For maintainers

  • A released version's files are held to scripts/released.json (every public/r file and docs page by hash),
    written by node scripts/released.mjs --write at RELEASING step 6 and checked by generated.mjs --check. The
    snapshot store in Vercel Blob, its scripts and workflow, and the upgrade fixtures and harness are gone.
  • released.mjs --write won't write over a record of the same dated version whose files differ (--force does, for
    a Release commit not yet merged), and --check also holds the record to the one tagged v<version>.
  • release:check warns on a note marking wording only the owner gives in any file that ships or is served, and fails
    on one under --full or once the version is dated.