Repository navigation
docs(i18n): refresh README source stamps after 4cf2d2cff - #7104
Merged
Merged
Conversation
4cf2d2c reworded the Computer Use paragraph in README.md and refreshed the content of all 18 translations, but left every 'source: README.md' stamp on the previous hash, so scripts/check-readme-translations.py fails on main with 'stale' for all 18 files. Bump the stamps; no prose changes. Signed-off-by: Boyce <aboyskyi@gmail.com>
3 tasks done
Hmbown
pushed a commit
to ddlw/Codewhale
that referenced
this pull request
Oct 27, 2026
Brings in codewhale-hq#7104's README stamp refresh, which the Lint leg's README translation check needs. On Windows `plan_launch` never assigns `native_snapshot_roots` (the field is `cfg(not(windows))`), so `let mut launch` failed `unused_mut` under -D warnings on Test (windows-latest); the non-Windows assignment is now a struct update. Maintainer fix on the contributor branch (CW-7525). Signed-off-by: CodeWhale Bot <bot@codewhale.net> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hmbown
pushed a commit
that referenced
this pull request
Oct 27, 2026
Fixes the three release-note gates that fail on main: - check-feature-release-notes / check-versions: commit 4cf2d2c references #7093 (multiline send key on Linux) and #7097 (relocated state root) with no changelog receipt. Both now have Unreleased entries describing the shipped source behavior. - check-bundled-plugin-claims: the first-party marketplace pin a5f1d21 (CW-6732, Computer Use runtime removed from the marketplace bundle) was never named in CHANGELOG.md. - check-contributor-credit: Boyce (@Aboysky, #7104) was uncredited. AUTHOR_MAP maps the commit email to the GitHub account; the changelog, docs/CONTRIBUTORS.md (new Unreleased band) and UNRELEASED_CONTRIBUTORS credit the window's code contributors. The Unreleased section gains a Contributors block so the 0.10.3 cut only has to rename the heading. crates/tui/CHANGELOG.md regenerated by scripts/sync-changelog.sh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3 tasks done
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.
What and why
4cf2d2c reworded the Computer Use paragraph in README.md and updated the content of all 18 translated READMEs to match, but the
source: README.md sha256:stamp at the top of each translation was left on the old hash. Soscripts/check-readme-translations.pyfails onmainright now with "stale" for all 18 files — the prose itself is already in sync, only the stamps lag.This PR bumps the stamps. No prose changes.
Issue
Refs #6804 — keeping the translations in lockstep with README.md is the sync work that issue calls for.
How I tested it
The same check fails on
mainbefore this change, with 18 "stale" stamp errors.One heads-up, unrelated to this PR: current
mainhas two pre-existing drifts I reproduced locally on this branch with only the stamp changes applied —cargo fmt --all -- --checkreports formatting drift incrates/tui/src/mcp.rs(two spots). The Lint check passed here anyway since fmt only runs for Rust-touching PRs; follow-up opened as chore(tui): re-apply rustfmt to mcp.rs #7106.Version driftcheck isscripts/check-bundled-plugin-claims.py: "first-party marketplace: pinned at a5f1d210372f…, which CHANGELOG.md never names". My commit touches only the 18 stamp lines, so this red is not from the PR — still happy to help with a separate commit if wanted.Checklist
mainmain, not from this PRdocs/features.tomlrow needed