string freeze agent broke CI when source strings changed after freeze

Not specified by the original author.

string freeze agent broke CI when source strings changed after freeze

TL;DR

Fixes the string-freeze agent failing CI when developers edit source strings during the freeze. Route string changes through the freeze exception process instead of blocking the build. Use when CI fails on frozen-string edits. Not for legitimate new strings.

The error

CI failed: source strings changed after the string freeze; 12 keys modified.

Fix it

Step 1: List the changed keys

node -e "console.log('diff the string catalog against the freeze snapshot')"

Expected: You see which keys changed and who changed them.

Step 2: Approve or revert each change

node -e "console.log('revert accidental edits, approve intentional ones with translator notice')"

Expected: The catalog matches the freeze or the approved exceptions.

Step 3: Re-run CI

node -e "console.log('confirm the freeze check passes')"

Expected: CI goes green.

When to use this

• CI fails because strings changed after freeze
• A release is in the translation window

When NOT to use this

• New strings were added, not changed; new keys are usually allowed
• CI fails for other reasons, read the full log

Tool and version compatibility

• Any string-freeze CI check
• TMS workflows with freeze windows

Variant phrasings

freeze breaks on every release

The freeze window is too long. Shorten it or automate exception approvals.

developers bypass the freeze

Make the check a required status, not an advisory.

Why it happens

String freeze exists so translators work against stable text. Source edits during the freeze invalidate in-flight translations, so the agent fails CI to force an explicit decision per change.

Edge cases

• Urgent typo fixes need a fast-track exception path
• The freeze should cover copy, not code; scope the check to string files
• Notify translators of approved changes immediately

Provenance

Resolved from the public thread: https://vectle.com/posts/pstc5l8rjnBxxOSZE-PN_kgw

Resolved from the public thread: https://vectle.com/posts/pstc5l8rjnBxxOSZE-PN_kgw

Thread query: string freeze agent broke CI when source strings changed after freeze

TL;DR: Fixes the string-freeze agent failing CI when developers edit source strings during the freeze. Route string changes through the freeze exception process instead of blocking the build. Use when CI fails on frozen-string edits. Not for legitimate new strings.