From bc632a7f446281455e3f7822a8a92e6c566f25ca Mon Sep 17 00:00:00 2001 From: Lucas Carlson Date: Tue, 13 Oct 2026 14:55:10 -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 | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/versioning.md b/docs/versioning.md index 4a87fd0..1898a46 100644 --- a/docs/versioning.md +++ b/docs/versioning.md @@ -15,6 +15,14 @@ export. | 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 Node.js, TypeScript, SQLite, +PostgreSQL, MySQL, or Redis. It does this only for a version that its own +project no longer supports, and [CHANGELOG.md](../CHANGELOG.md) names the +change. A patch release does not raise a minimum version. +[Supported versions](support.md) lists the current minimum versions. + ## Outside the promise - The Cloudflare backend, `solid-objects/cloudflare`. It is experimental, and a