Carries the upgrading page's title and pin list to 0.23 - #247
Merged
Merged
Conversation
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
johnnyt
force-pushed
the
sp-4cy9-upgrading-page-to-023
branch
from
September 30, 2026 06:08
6f63286 to
ac8ce10
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
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. This carries those four sites to 0.23 and changes nothing else on the page:
"~> 0.23.0"(the README's install pin is already~> 0.23.0);Refs: sp-4cy9
Gate
This branch touches only
docs/upgrading.md, outside the gate's build paths, so there is no gate to run (the repo's commit authority row: a change touching no Elixir code commits on review of the diff alone). CI runs the full gate on this request. No changelog fragment: documentation only, perchangelog.d/README.md.Review
Own review of the diff against the bead: one file changed, the four sites named above and no others; the "0.22 to 0.23" section and its "0.23.1" subsection are untouched. The schema claim was checked against the code:
StatifierPersistence.Ecto.Migrationscomputes@current_versionfrom its migrations map, whose modules areV01throughV08underlib/statifier_persistence/ecto/migrations/, and no commit since the v0.22.0 tag touches that directory ormigrations.ex. The "every later release keeps it there" sentence on thestatifierfloor still holds:mix.exspins{:statifier, "~> 2.9"}.