solid_objects 1.0.2 → 1.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 556d59f2ef4f4862b2d8a851f19ce31b2eca80b6ebb1ea45a8f1dce9c7c1e122
-  data.tar.gz: b9c1539d5cff7ea9a75e24268771cabe1571a5b0688fec187bfddc255189c4e5
+  metadata.gz: 1f327f61b104201a040880d246844ce1b3a3b2c8cb839c74b6f84e737fc06935
+  data.tar.gz: 7535fe51e3dad72ac0182fcc4b2ae250eaa16cb88c61bf16e3714d3b4553c5db
 SHA512:
-  metadata.gz: dc9a3b2e02e0c769d459eb9fbab94d1f86553a2ea4841356b32a2288dee8a6294cd4db285fa5ccf730e7ab329d1189c11f91736825d27411caa63befc94d0f48
-  data.tar.gz: 6becd234cc81dd86b766b8be4c793e31b852093f4a4ec31b6548c6cd61b7b5ef2a103a0fc5f713d52b03349eab547726f1a00fe074c7885a5a17ad3ac6b9b753
+  metadata.gz: fda52296b4996e169a1ca71b6754be4c98f2ecd3d3eac8dd22ed9dfee3972a715117a9320c7c4d1cceaf413c4dce677660b3a63670b577a293e0c987d75ca269
+  data.tar.gz: 02e527b45cc20105242f3ff561af5573853b97bbbda4974b34ec1cc5ace30eec08ad27922ff6e4d8a339a26b08969aeebd0484edd9e427cb2c2a501a1f5720f6

data/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 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 gem, how CI checks
+  each change, how a release is published, what you keep if maintenance
+  stops, and how to become a maintainer. The README and the comparison pages
+  now link to this page. They and `docs/versioning.md` no longer state a count
+  of maintainers. A new test fails when a page states one.
+
 ## 1.0.2 - 2026-10-15
 
 - Add two comparison pages in `docs/compare/`: Solid Queue

data/README.md

@@ -13,12 +13,11 @@ 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 6, 2026. One maintainer.
+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.
@@ -199,6 +198,7 @@ every claim in [`test/guides/`](test/guides/):
 - [Reminders](docs/reminders.md)
 - [Reactive ERB](docs/realtime.md)
 - [Detailed architecture](docs/architecture.md)
+- [Maintenance and continuity](docs/maintenance.md)
 - [Detailed documentation](docs/)
 
 The dashboard, benchmarks, migration cookbook, schema, and exhaustive API
@@ -207,10 +207,8 @@ explanations remain in `docs/`. The README stops here.
 ## Status and license
 
 Version 1.0 promises a stable public API. Its correctness core is tested
-against SQLite, PostgreSQL, and MySQL. 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 change.
+against SQLite, PostgreSQL, and MySQL. [Versioning](docs/versioning.md) says
+what a release can change.
 
 Solid Objects is released under the [MIT License](MIT-LICENSE). It is an
 independent project and is not affiliated with, sponsored by, or endorsed by

data/docs/compare/good-job.md

@@ -210,7 +210,7 @@ How it works:
 
 - First public release: August 6, 2026.
 - Version 1.0.0: October 13, 2026. The public API follows [semantic versioning](../versioning.md).
-- One maintainer.
+- [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.
 

data/docs/compare/solid-queue.md

@@ -205,7 +205,7 @@ How it works:
 
 - First public release: August 6, 2026.
 - Version 1.0.0: October 13, 2026. The public API follows [semantic versioning](../versioning.md).
-- One maintainer.
+- [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.
 

data/docs/comparisons.md

@@ -23,4 +23,4 @@ The problem guides start from the same choices:
 
 ## Status
 
-Solid Objects 1.0.0 shipped on October 13, 2026. The first public release was on August 6, 2026. It has one maintainer. 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. See [versioning](versioning.md).
+Solid Objects 1.0.0 shipped on October 13, 2026. The first public release was on August 6, 2026. 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. See [versioning](versioning.md) and [maintenance and continuity](maintenance.md).

data/docs/maintenance.md

@@ -0,0 +1,65 @@
+# Maintenance and continuity
+
+This page tells you who maintains Solid Objects, how a release is made, and
+what you keep if maintenance stops. It also tells you how to help maintain the
+project.
+
+## Who maintains it
+
+Lucas Carlson ([@cardmagic](https://github.com/cardmagic)) is the lead
+maintainer of the Ruby gem `solid_objects` and of the npm package
+[`solid-objects`](https://github.com/cardmagic/solid-objects-js). The two
+packages use the same model and the same correctness contract. A change to the
+model goes into both packages, and the
+[parity ledger](https://github.com/cardmagic/solid-objects-js/blob/main/docs/parity.md)
+records each difference between them.
+
+The same maintainer sells [Solid Objects Pro](https://solidobjects.pro), a
+commercial package that batches operations at scale. Pro depends on this gem.
+This gem does not depend on Pro, and it needs no account, license key, or
+service from the maintainer.
+
+## How a change is checked
+
+CI runs on each push and each pull request:
+
+- The full test suite on SQLite, on each pair of Ruby 3.3, 3.4, or 4.0 and
+  Rails 7.1, 7.2, 8.0, or 8.1.
+- The full test suite on PostgreSQL and on MySQL, with both MySQL clients.
+- Standard, RuboCop, RBS, Steep, and Brakeman.
+
+[Compatibility and maturity](virtual-actors.md#compatibility-and-maturity)
+lists the supported versions. The [correctness contract](correctness.md) lists
+the guarantees that the tests check.
+
+## How a release is made
+
+1. The maintainer pushes a version tag, for example `v1.0.3`.
+2. GitHub Actions runs all test jobs again on that tag.
+3. If all test jobs pass, GitHub Actions builds the gem and pushes it to
+   RubyGems with trusted publishing. The repository keeps no RubyGems key.
+4. The same job makes a GitHub release and attaches the gem file.
+
+[Versioning](versioning.md) tells you what a release can change.
+`CHANGELOG.md` lists each release.
+
+## What you keep if maintenance stops
+
+- **Your data.** Actor state, mailboxes, reminders, and effects are rows in
+  your application's database. [Database schema](database-schema.md) describes
+  each table. No service of the maintainer holds your data.
+- **The code.** The [MIT License](../MIT-LICENSE) lets anyone use, change,
+  fork, and publish the code.
+- **The checks.** The tests and the CI configuration are in this repository. A
+  fork can check its changes with the same suite.
+
+## Help maintain Solid Objects
+
+The project wants more maintainers. Experience with Rails, with locks and
+transactions in PostgreSQL or MySQL, or with TypeScript and Node.js helps.
+
+1. Read [CONTRIBUTING.md](../CONTRIBUTING.md).
+2. Send a small pull request: a fix, a test, or a correction to a guide.
+3. After some of your pull requests are merged, open an
+   [issue](https://github.com/cardmagic/solid-objects-ruby/issues) to ask to
+   become a maintainer.

data/docs/versioning.md

@@ -41,8 +41,8 @@ lists the current minimum versions.
 
 Version 1.0 is a promise about the API. It is not a claim of measured scale.
 The [benchmarks](benchmarks.md) are development measurements and do not
-guarantee capacity. Longer soak tests are open work. The project has one
-maintainer, and no production use by other people is known.
+guarantee capacity. Longer soak tests are open work. No production use by
+other people is known.
 
 ## Releases before 1.0
 

data/lib/solid_objects/version.rb

@@ -1,5 +1,5 @@
 # rbs_inline: enabled
 
 module SolidObjects
-  VERSION = "1.0.2"
+  VERSION = "1.0.4"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: solid_objects
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.0.4
 platform: ruby
 authors:
 - Lucas Carlson
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-10-15 00:00:00.000000000 Z
+date: 2026-10-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: actioncable
@@ -372,6 +372,7 @@ files:
 - docs/guides/transactional-outbox.md
 - docs/implementation-plan.md
 - docs/local-testing.md
+- docs/maintenance.md
 - docs/migrating-existing-state.md
 - docs/observability.md
 - docs/operations.md