manual-translation-clobbered: hand-edited translation overwritten
warning — advisory, exit 0
A translation you locked as hand-edited (shipi18n lock) has been overwritten with different text — typically by a bulk retranslation run that did not know a human had already fixed that string.
What triggers it
// locks.json records the hand-fixed value…
// …but es.json now contains a different, regenerated string.Fixed
// es.json matches the locked, hand-edited value.Why it matters
Human fixes are the most expensive translations you own. Locks exist so a machine never silently undoes one — and this finding is deliberately a warning, because protecting human work should never fail a pipeline.
How to fix it
Restore the locked value, or if the new text is genuinely better, re-lock it: shipi18n lock --relock.
How to silence it
--no-locks disables lock checking entirely; prefer re-locking the intended value.
Check for this in CI
npx @shipi18n/cli check ./locales -s en
# SARIF for inline PR annotations:
npx @shipi18n/cli check ./locales -s en -r sarif -o shipi18n.sarifThe structural checks need no API key. Findings of this rule link back to this page from the SARIF helpUri.
Related rules
- manual-translation-stale — source changed after a manual translation was locked