Skip to content
RoutingCatRoutingCatRoutingCat Docs

Changelog

What each version of the routingcat package brings that you, or your coding agent, should know: what is new and worth reading about, and what now works differently. The docs and the skill always describe the current version in full; this page points to what changed. npx routingcat@latest upgrade installs the latest version and shows the entries between yours and it.

1.1.0

Published 2026-11-10.

  • New: conditions. A variant can show only to some visitors, or never to some, by only and never in code or npx routingcat set --only and --never, over RoutingCat’s dimensions and your own. Read Show a variant only to some visitors.
  • New: your own dimensions, audiences and expectations. Group your campaigns, ads and sources into levels that conditions name and results break down by, name a condition for reuse, start routing from where you expect a variant to do better, and let a slot learn by a dimension of yours with personalizeBy. npx routingcat dimensions and audiences list them. Read Show a variant only to some visitors and Routing settings.
  • New: values. An objective can say what each of its events is worth, so that routing optimizes the value per visit (VPV), the conversion rate times the value per conversion, in your value’s own unit, as you define it, and status leads with the measured value gain. Read Optimize for what a visit is worth, which also says what a value should count.
  • New: Next.js on your own Node.js server. RoutingCat runs on a Next.js site your own server serves with next start, set up with npx routingcat init --host node, and routing uses your visitors’ locations where you declare Cloudflare in front. Read Your own Node.js server.
  • Changed: the ad network and paid traffic. Each visit’s ad network becomes a dimension, --by ad_network, and sources splits paid traffic into paid_search, paid_social and paid, once every deployment of your site runs 1.1.0. Read Upgrade to 1.1.

What to do: deploy every deployment of your site, previews still in use included, before you rely on a condition: until each one that built, started or recorded visits in the last 72 hours runs 1.1.0, a variant with a condition is shown to no visitor. Tag your Meta ads’ links with a Meta source and a paid medium, as utm_source=facebook&utm_medium=paid_social: with a paid medium but no Meta source, their visits count as other. Read Upgrade to 1.1.

1.0.6

Published 2026-11-08.

  • New: Whop Websites and TanStack Start, experimental. RoutingCat runs inside a Whop Website, installed from one prompt in Whop’s AI builder or with npx routingcat init. Read Whop Websites.
  • New: npx routingcat@latest upgrade moves your project to the latest version, its skill with it. Read Run it in production.
  • Changed: npx routingcat connect whop proves your Whop account with your key by default, and reads the key from ROUTINGCAT_WHOP_KEY, no longer WHOP_API_KEY. On a Whop Website it refuses, since the Website connects its payments itself. Read Whop.

What to do: where you set WHOP_API_KEY for connect whop, set ROUTINGCAT_WHOP_KEY instead.

1.0.5

Published 2026-11-01.

Nothing that changes how you work with RoutingCat.

1.0.4

Published 2026-10-29.

  • Changed: lowering the random slice below 5% waits for your confirmation, as lowering the control does: npx routingcat set takes --confirm for it.

1.0.3

Published 2026-10-27.

  • Changed: lowering the control below 5% waits for your confirmation: npx routingcat set takes --confirm for it.
  • Changed: on Next.js, a static page builds every combination of the variants it serves at deploy, up to 1,000 copies per page.

1.0.2

Published 2026-10-26.

Nothing that changes how you work with RoutingCat.

1.0.1

Published 2026-10-26.

Nothing that changes how you work with RoutingCat.

1.0.0

Published 2026-10-25.

The first version.

Next

RoutingCat routes each visitor of your site to the variants that convert.