From 2dedbe6a548b4e369603ae6c599661290a14c92e Mon Sep 17 00:00:00 2001 From: Lucas Carlson Date: Fri, 9 Oct 2026 10:17:45 -0700 Subject: [PATCH 1/2] docs: say that Solid Objects Pro ships for Node.js The agent guide and the fit guide said that the Node build of Solid Objects Pro was in development. @solidobjects/pro ships today from the private registry at solidobjects.pro, beside the Rails gem, so an agent that read the old text ruled out Pro for a Node.js hot key. --- docs/agents.md | 30 +++++++++++++++--------------- docs/fit.md | 4 ++-- 2 files changed, 17 insertions(+), 17 deletions(-) diff --git a/docs/agents.md b/docs/agents.md index f4b0cca..3768a30 100644 --- a/docs/agents.md +++ b/docs/agents.md @@ -19,27 +19,27 @@ Use Solid Objects only if you can answer yes to most of these questions: Select a simpler tool in these cases: -| Requirement | Use instead | -| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | -| The invariant fits in one request | A transaction, a constraint, or `SELECT ... FOR UPDATE` | -| CPU-intensive or parallel work | `worker_threads` or a worker pool. An actor serializes work | -| Thousands of writes for each second to one key | A counter column or a cache. Solid Objects Pro covers this case for Rails; its Node build is in development | -| One atomic change across two actor identities | One SQL transaction on normal tables | -| Exactly-once calls to an external API | Not available from any actor library. Use provider idempotency keys | -| Replay of named workflow steps from a step log | A durable execution engine, such as DBOS or Temporal | +| Requirement | Use instead | +| ---------------------------------------------- | ---------------------------------------------------------------------------------- | +| The invariant fits in one request | A transaction, a constraint, or `SELECT ... FOR UPDATE` | +| CPU-intensive or parallel work | `worker_threads` or a worker pool. An actor serializes work | +| Thousands of writes for each second to one key | A counter column, a cache, or Solid Objects Pro, which ships for Node.js and Rails | +| One atomic change across two actor identities | One SQL transaction on normal tables | +| Exactly-once calls to an external API | Not available from any actor library. Use provider idempotency keys | +| Replay of named workflow steps from a step log | A durable execution engine, such as DBOS or Temporal | The full list is in [Choosing Solid Objects](fit.md). The category guide is [Virtual actors in TypeScript and Node.js](virtual-actors.md). ## 2. Package identity -| Item | Value | -| ------------------ | ----------------------------------------------------------------------------------------------------- | -| npm package | `solid-objects` | -| Repository | | -| Website | | -| Ruby on Rails gem | `solid_objects`, a separate implementation of the same model | -| Commercial package | `@solidobjects/pro`, a separate paid package in development. The open-source package does not need it | +| Item | Value | +| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| npm package | `solid-objects` | +| Repository | | +| Website | | +| Ruby on Rails gem | `solid_objects`, a separate implementation of the same model | +| Commercial package | `@solidobjects/pro`, a separate paid package from the private registry at . The open-source package does not need it | Solid Objects is not SolidJS and has no relation to it. It is not affiliated with Cloudflare. diff --git a/docs/fit.md b/docs/fit.md index f342e15..3962a99 100644 --- a/docs/fit.md +++ b/docs/fit.md @@ -42,8 +42,8 @@ history, and no actor-state migration contract. fits, because each check is one durable ordered message. For the high-QPS limiter, see [Solid Objects Pro](https://solidobjects.pro/): grouped commits coalesce concurrent writes into one insert, and ephemeral operations keep - loss-tolerant calls out of the durable journal. It ships for the Rails gem - today, and the Node build is in development. Distributed per-actor rate + loss-tolerant calls out of the durable journal. It ships for Node.js as + `@solidobjects/pro` and for the Rails gem. Distributed per-actor rate limits, global admission control, and cache-capacity eviction are answered there rather than in this runtime, and are not open roadmap items here. - Durable workflow replay across named steps is more important than a mutable From 7a8ad67f7dbd8247266ddaec6695253a9b68a6ed Mon Sep 17 00:00:00 2001 From: Lucas Carlson Date: Fri, 9 Oct 2026 10:17:46 -0700 Subject: [PATCH 2/2] chore: prepare version 0.17.5 --- CHANGELOG.md | 7 +++++++ package.json | 2 +- src/version.ts | 2 +- 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 526b1c9..fa6c371 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,12 @@ # Changelog +## 0.17.5 - 2026-10-09 + +- Correct `docs/agents.md` and `docs/fit.md`: Solid Objects Pro ships for + Node.js as `@solidobjects/pro` from the private registry at + , beside the Rails gem. The docs said that its + Node build was in development. + ## 0.17.4 - 2026-10-08 - Step 12 of `docs/agents.md` now says plainly that every authorization diff --git a/package.json b/package.json index e5a4339..9506789 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "solid-objects", - "version": "0.17.4", + "version": "0.17.5", "description": "SQL-backed virtual actor library for TypeScript and Node.js, with durable state, ordered operations, and automatic activation on SQLite, PostgreSQL, or MySQL", "type": "module", "license": "MIT", diff --git a/src/version.ts b/src/version.ts index 1e87784..cd1e341 100644 --- a/src/version.ts +++ b/src/version.ts @@ -1 +1 @@ -export const VERSION = "0.17.4" +export const VERSION = "0.17.5"