Write the upgrade guide in English - #303
Merged
Merged
Conversation
`UPGRADE.md` is what a consumer reads when a release breaks something, and the third half of the repository's own rule: Rector first, a script when Rector cannot, documentation in every case. Several sections say plainly that Rector cannot help and why — that is the point of the file, and it survives intact. Everything a reader copies is byte-identical, and that is checked rather than claimed: the eight fenced blocks diff clean except two comment lines, the fifteen headings keep their level and order, `## 0.1.0-alpha8` is untouched, and the set of backticked symbols outside fences — every class, interface, attribute, constant, service id and config key — is identical before and after. The two comment lines that did move are inside fences, one `//` in the `rector.php` sample and one `#` in the tags YAML, each with its code and its column alignment unchanged. A French comment left in an English guide would be the visible defect the fence rule exists to prevent. The three tables were realigned rather than left ragged: English is not the width of French, and each table now has exactly one pipe layout. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
gplanchat
enabled auto-merge
September 7, 2026 23:13
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.
UPGRADE.md, 324 lines, French from top to bottom. It is what a consumer reads when a releasebreaks something — the "documentation in every case" half of this repository's own rule.
What is checked, not claimed
compared in order:
composer require,vendor/bin/rector process src, therector.phpsample,both
bin/console cache:clear, thedurable.nexus_handler: … is served by nobodyoutput and thetags YAML are what a reader copies, and they are untouched.
//in therector.phpsample,one
#in the tags YAML — each with the code on its line and its column alignment unchanged. Thebrief named
//only; the agent translated the#too and flagged it as a decision rather thanan oversight. It was right: a French comment left inside an English guide is the visible defect
the fence rule exists to prevent.
## 0.1.0-alpha8is byte-identical.## Non publiébecomes## Unreleased, which is prose.a multiset. That covers
durable.event_store.dbal,Gplanchat\Durable\Store\EventStoreInterface,AsActivityHandler,MEMO_KEY_JOURNAL_BOOTSTRAP, and the\BadMethodCallExceptionversusBadMethodCallExceptiondistinction, which the file makes deliberately and keeps.has exactly one pipe layout, and each keeps its own separator style.
After this
Nothing French is left outside
documentation/(whose*.fr.mdare WA006's own exception),.cursor/(another tool's configuration),openspec/(point-in-time records) and the twosupervised scripts
bin/splitsh-publish.shandbin/prises-check*.sh— the second of which printsthe French you see in the "Stale claims and titles" check.