From 240f3e273084dede37876fd3c76f6ad93663a25f Mon Sep 17 00:00:00 2001 From: Lucas Carlson Date: Tue, 13 Oct 2026 14:55:08 -0700 Subject: [PATCH] docs: say when a release can drop a runtime The versioning document did not say if a minor release can raise the minimum version of a language runtime or a database. A reader could not tell what to expect for all of 1.x. A minor release can raise a minimum version, but only for a version that its own project no longer supports. A patch release cannot. One maintainer then does not carry unsupported versions until 2.0. --- docs/versioning.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/versioning.md b/docs/versioning.md index 3a00174..7953a53 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -14,6 +14,15 @@ configuration options that `README.md` and the files in `docs/` describe. | Minor, for example 1.1.0 | New behavior. Code that uses the public API continues to work | | Major, for example 2.0.0 | A change that breaks code that uses the public API | +## Supported versions + +A minor release can raise the minimum version of Ruby, Rails, SQLite, +PostgreSQL, or MySQL. It does this only for a version that its own project no +longer supports, and `CHANGELOG.md` names the change. A patch release does not +raise a minimum version. +[Compatibility and maturity](virtual-actors.md#compatibility-and-maturity) +lists the current minimum versions. + ## Outside the promise - Classes, methods, and constants that the documentation does not describe.