From ac8ce102fb6615fed8c26c66cb1182a3f6e5b3ef Mon Sep 17 00:00:00 2001 From: JohnnyT Date: Wed, 30 Sep 2026 00:05:22 -0600 Subject: [PATCH] Carries the upgrading page's title and pin list to 0.23 The upgrading page gained its "0.22 to 0.23" section, but its title, opening paragraph, pin chain and schema sentence still stopped at 0.22. The title now reads 0.13 to 0.23, the opening paragraph moves a host from 0.13.0 to 0.23.0, the pin chain ends with `"~> 0.23.0"`, and the schema sentence says no release from 0.18.0 through 0.23.0 adds a migration, nor does the 0.23.1 patch: the migrations module still holds V01 through V08, unchanged since v0.22.0. Nothing else on the page changes. A change touching no Elixir code; the diff is outside the gate's build paths, so there is no gate to run and it commits on review of the diff. No changelog fragment: documentation only. Refs: sp-4cy9 --- docs/upgrading.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/upgrading.md b/docs/upgrading.md index 0358e06..d29ab04 100644 --- a/docs/upgrading.md +++ b/docs/upgrading.md @@ -1,7 +1,7 @@ -# Upgrading a host from 0.13 to 0.22 +# Upgrading a host from 0.13 to 0.23 This page says what a host changes to move `statifier_persistence` from -0.13.0 to 0.22.0, one minor at a time. A host here is the code that +0.13.0 to 0.23.0, one minor at a time. A host here is the code that embeds the package: the module that calls `use StatifierPersistence.Ecto`, the migrations it runs, the options it passes to `StatifierPersistence.Executions` and `StatifierPersistence.Driver`, the @@ -13,7 +13,8 @@ nothing. Take the minors in order, and move the pin with each one, as the README recommends: `{:statifier_persistence, "~> 0.14.0"}`, then `"~> 0.15.0"`, then `"~> 0.16.0"`, then `"~> 0.17.0"`, then `"~> 0.18.0"`, then -`"~> 0.19.0"`, then `"~> 0.20.0"`, then `"~> 0.21.0"`, then `"~> 0.22.0"`. +`"~> 0.19.0"`, then `"~> 0.20.0"`, then `"~> 0.21.0"`, then `"~> 0.22.0"`, +then `"~> 0.23.0"`. The `statifier` floor stays `~> 2.6` through 0.17.0; 0.18.0 moves it to `~> 2.9`, and every later release keeps it there. @@ -33,7 +34,8 @@ with its own migration, and an install still short of V06 follows the V06 ordering rule in the `StatifierPersistence.Ecto.Migrations` documentation first. No release before 0.17.0 adds a migration; 0.17.0 does (V08, under "0.16 to 0.17"), and -no release from 0.18.0 through 0.22.0 adds one. +no release from 0.18.0 through 0.23.0 adds one, and neither does the +0.23.1 patch. ## 0.13 to 0.14