Changelog
Two kinds of releases appear here:
- Platform YYYY.MM.DD: the lab and the manager server. Released each time production is deployed. Nothing to upgrade.
-
CLI X.Y.Z: the
pairitcommand-line tool on npm. Upgrade with:
Full release notes are on GitHub Releases.
Unreleased
Merged, but not released yet.
Platform
CLI
Platform 2026.10.18
- Chat avatars can come from
session_state, e.g. a different avatar per group member with a distributed randomization. See Avatars from session state. - Action needed: an avatar is now a single string, an icon name or an image path. Replace
avatar: { icon: bot }withavatar: bot, andavatar: { image: /a.png }withavatar: /a.png, in agents and in chatavatars. The old form no longer works; it shows the default avatar. - New example: Fruit split demo.
CLI 0.3.2
pairit config lintchecks randomization that usesdistribute: true: it needsscope: group, and itsconditionslist must have one entry per group member. See Different roles within a group.
CLI 0.3.1
- In a split layout,
pairit config lintchecks that each component'scolumnisleftorright. See Split layout. --env stagingand--env productionnow take precedence overPAIRIT_API_URL.
CLI 0.3.0
- Upload configs with
--nameinstead of--config-id. Pairit builds the participant link from the name with a random suffix, e.g.my-study-k3f9x2m8q1. - Re-uploading under the same name keeps the link and saves a new revision. The CLI warns you if participants already ran the previous one.
pairit config history <configId>lists revisions and their session counts.- The sessions export has a
configRevisioncolumn.
Existing links don't change. See Names, links, and revisions.