solid-objects 1.0.3 → 1.0.5

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 1.0.5 - 2026-10-18
+
+- `docs/versioning.md` is now the only page that states that version 1.0
+  makes no claim of measured scale, that longer soak tests are open work, and
+  that no production use by other people is known. The comparison pages,
+  `docs/agents.md`, `docs/virtual-actors.md`, and the problem guides link it
+  instead. The comparison pages no longer state the first public release
+  date.
+
+## 1.0.4 - 2026-10-18
+
+- The README no longer states the first public release date, that no
+  production use by other people is known, that longer soak tests are open
+  work, or that version 1.0 makes no claim of measured scale.
+  `docs/versioning.md` keeps the other three limits, and the README links it.
+  The comparison pages keep the first public release date.
+
 ## 1.0.3 - 2026-10-18
 
 - Add `docs/maintenance.md`. It tells you who maintains the package, how CI

package/README.md

@@ -13,12 +13,11 @@ explains the model and when to use it.
 
 **Status.** Version 1.0: the public API follows semantic versioning and does
 not break before 2.0. [Versioning](docs/versioning.md) gives the limits of the
-promise. First public release: August 13, 2026.
+promise.
 
 **Production use.** One first-party application with more than 100,000 users
-runs it in production. That is a count of users, not a measure of load. No
-production use by other people is known. The [benchmarks](docs/benchmarks.md)
-are development measurements, and longer soak tests are open work.
+runs it in production. That is a count of users, not a measure of load. The
+[benchmarks](docs/benchmarks.md) are development measurements.
 
 **It is not** Solid Queue, SolidJS, or the `service_actor` gem, and it is not
 affiliated with Rails or Cloudflare.
@@ -304,9 +303,7 @@ notes remain in `docs/`, where long documentation can be long on purpose.
 
 Version 1.0 promises a stable public API. The correctness core has automated
 coverage across the supported databases, browser runtime, recovery paths, and
-packaged artifact. It makes no claim of measured scale: the
-[benchmarks](docs/benchmarks.md) are development measurements, and longer soak
-tests are open work. [Versioning](docs/versioning.md) says what a release can
+packaged artifact. [Versioning](docs/versioning.md) says what a release can
 change. The Cloudflare backend is experimental and is outside that promise.
 
 Solid Objects is released under the [MIT License](MIT-LICENSE). It is an

package/dist/version.d.ts

@@ -1,2 +1,2 @@
-export declare const VERSION = "1.0.3";
+export declare const VERSION = "1.0.5";
 //# sourceMappingURL=version.d.ts.map

package/dist/version.js

@@ -1,2 +1,2 @@
-export const VERSION = "1.0.3";
+export const VERSION = "1.0.5";
 //# sourceMappingURL=version.js.map

package/docs/agents.md

@@ -347,8 +347,8 @@ When you explain Solid Objects to a user, state these limits:
 - There are no transactions across actor identities.
 - Fencing stops a stale activation from a commit, but its code can continue to
   run.
-- Version 1.0 promises a stable public API. It makes no claim of measured scale,
-  and no production use by other people is known.
+- Version 1.0 promises a stable public API. [Versioning](versioning.md) states
+  the limits of that promise.
 - `solid-objects/browser` is a WebSocket client, not the SQL runtime. The
   browser runtime in step 12 is tested in Chromium only. The Cloudflare backend
   is experimental and is outside the version 1.0 promise.

package/docs/compare/dbos.md

@@ -351,11 +351,10 @@ How it works:
 
 **Is Solid Objects mature enough?** Here are the facts:
 
-- First public release of the npm package: August 13, 2026.
 - Version 1.0.0: October 13, 2026. The public API follows [semantic versioning](../versioning.md).
 - [Maintenance and continuity](../maintenance.md) tells you who maintains the project and how a release is made.
-- One first-party application with more than 100,000 users runs it in production. That is a count of users, not a measure of load. No production use by other people is known.
-- The [benchmarks](../benchmarks.md) are development measurements. Longer soak tests are open work.
+- One first-party application with more than 100,000 users runs it in production. That is a count of users, not a measure of load.
+- The [benchmarks](../benchmarks.md) are development measurements. [Versioning](../versioning.md) states what version 1.0 does not claim.
 
 DBOS has a company, a hosted service, and a longer history. If those matter more than state for each cart, choose DBOS.
 

package/docs/compare/graphile-worker.md

@@ -256,11 +256,10 @@ How it works:
 
 **Is Solid Objects mature enough?** Here are the facts:
 
-- First public release of the npm package: August 13, 2026.
 - Version 1.0.0: October 13, 2026. The public API follows [semantic versioning](../versioning.md).
 - [Maintenance and continuity](../maintenance.md) tells you who maintains the project and how a release is made.
-- One first-party application with more than 100,000 users runs it in production. That is a count of users, not a measure of load. No production use by other people is known.
-- The [benchmarks](../benchmarks.md) are development measurements. Longer soak tests are open work.
+- One first-party application with more than 100,000 users runs it in production. That is a count of users, not a measure of load.
+- The [benchmarks](../benchmarks.md) are development measurements. [Versioning](../versioning.md) states what version 1.0 does not claim.
 
 **Why Node.js 24.4 or newer?** The SQLite adapter reads integer columns as `BigInt`. Node.js 24.4.0 is the first release that accepts `readBigInts` on the built-in SQLite module. See [support](../support.md).
 

package/docs/compare/restate.md

@@ -252,11 +252,10 @@ A model call can run again after a crash, because effects run at least once. If
 
 **Is Solid Objects mature enough?** Here are the facts:
 
-- First public release of the npm package: August 13, 2026.
 - Version 1.0.0: October 13, 2026. The public API follows [semantic versioning](../versioning.md).
 - [Maintenance and continuity](../maintenance.md) tells you who maintains the project and how a release is made.
-- One first-party application with more than 100,000 users runs it in production. That is a count of users, not a measure of load. No production use by other people is known.
-- The [benchmarks](../benchmarks.md) are development measurements. Longer soak tests are open work.
+- One first-party application with more than 100,000 users runs it in production. That is a count of users, not a measure of load.
+- The [benchmarks](../benchmarks.md) are development measurements. [Versioning](../versioning.md) states what version 1.0 does not claim.
 
 Restate reached 1.0 in June 2024. If a longer history matters more than keeping the state in your own database, choose Restate.
 

package/docs/compare/rivetkit.md

@@ -244,11 +244,10 @@ How it works:
 
 **Is Solid Objects mature enough?** Here are the facts:
 
-- First public release of the npm package: August 13, 2026.
 - Version 1.0.0: October 13, 2026. The public API follows [semantic versioning](../versioning.md).
 - [Maintenance and continuity](../maintenance.md) tells you who maintains the project and how a release is made.
-- One first-party application with more than 100,000 users runs it in production. That is a count of users, not a measure of load. No production use by other people is known.
-- The [benchmarks](../benchmarks.md) are development measurements. Longer soak tests are open work.
+- One first-party application with more than 100,000 users runs it in production. That is a count of users, not a measure of load.
+- The [benchmarks](../benchmarks.md) are development measurements. [Versioning](../versioning.md) states what version 1.0 does not claim.
 
 **Why Node.js 24.4 or newer?** The SQLite adapter reads integer columns as `BigInt`. Node.js 24.4.0 is the first release that accepts `readBigInts` on the built-in SQLite module. See [support](../support.md).
 

package/docs/guides/persistent-rooms.md

@@ -383,7 +383,7 @@ The seventh test does not inject a late or repeated timer. The turn number check
 
 Delivery is at least once. Write each operation so that it can run again. One room runs one write at a time. This fits turn-based play, not a high-frequency game loop or fast real-time physics.
 
-The application owns the WebSocket server, authentication, and the display of the room. There are no transactions across two rooms. The package requires Node.js 24.4 or newer and ESM only. Version 1.0 promises a stable public API. It makes no claim of measured scale.
+The application owns the WebSocket server, authentication, and the display of the room. There are no transactions across two rooms. The package requires Node.js 24.4 or newer and ESM only. Version 1.0 promises a stable public API. [Versioning](../versioning.md) states the limits of that promise.
 
 See [Correctness and delivery semantics](../correctness.md) and [Virtual actors in TypeScript and Node.js](../virtual-actors.md).
 

package/docs/guides/race-conditions.md

@@ -355,7 +355,7 @@ There are no transactions across two actor identities. One identity runs one wri
 
 Each operation adds a message row. The runtime keeps completed messages for 30 days by default through `messageRetentionMilliseconds`. See [Configuration](../configuration.md#retention-and-cleanup) for retention and cleanup controls.
 
-The package requires Node.js 24.4 or newer and supports ESM only. Version 1.0 promises a stable public API. It makes no claim of measured scale. See [Correctness and delivery semantics](../correctness.md) and [Virtual actors in TypeScript and Node.js](../virtual-actors.md).
+The package requires Node.js 24.4 or newer and supports ESM only. Version 1.0 promises a stable public API. [Versioning](../versioning.md) states the limits of that promise. See [Correctness and delivery semantics](../correctness.md) and [Virtual actors in TypeScript and Node.js](../virtual-actors.md).
 
 ## Sources
 

package/docs/virtual-actors.md

@@ -246,10 +246,9 @@ These runtimes have different compatibility statements:
 | Browser runtime (`solid-objects/browser/host`)  | The actor runtime in a browser module worker on SQLite WASM. Tested in Chromium                                                                |
 | Cloudflare backend (`solid-objects/cloudflare`) | Experimental. It runs the actor API on Cloudflare Durable Objects, with different capability limits                                            |
 
-Version 1.0: the public API follows [semantic versioning](versioning.md). The
-Cloudflare backend is outside that promise. One first-party application with
-more than 100,000 users runs the package in production. That is a count of
-users, not a measure of load. The project makes no claim of measured scale,
-and no production use by other people is known.
+Version 1.0: the public API follows [semantic versioning](versioning.md),
+which also states the limits of that promise. The Cloudflare backend is outside
+that promise. One first-party application with more than 100,000 users runs the
+package in production. That is a count of users, not a measure of load.
 [Supported versions](support.md) lists the CI matrix. For Ruby on Rails, use
 the [solid_objects](https://github.com/cardmagic/solid-objects-ruby) gem.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "solid-objects",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "description": "Fix race conditions across Node.js processes: ordered operations, expiring holds, and state that survives a restart, in your SQL database. A SQL-backed virtual actor library for TypeScript and Node.js.",
   "type": "module",
   "license": "MIT",