Track @v0 in the fa and zh-cn sync workflows#584
Merged
Conversation
Completes the pin migration this repo started for French in #581. Translation happens in the source repo's sync workflow, so these two pins govern what engine version actually translates fa and zh-cn content — and they were still on `@v0.16.1`, two releases behind. Floating `@v0` is the policy settled in QuantEcon/project-translation#9: it is the action's own documented convention, its floating tags are well maintained, and development tempo is fast enough that hand-bumping reliably lags the releases worth having. The residual 0.x-may-break risk is mitigated not by the pin but by sync output landing as a PR a human reviews before merge. With these two, all nine translation workflow pins across the programming trio track `@v0`, so future releases reach production on merge rather than needing a rollout PR each time. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR completes the repo’s migration of translation sync workflows to track the floating QuantEcon/action-translation@v0 tag, aligning the fa and zh-cn source-side sync workflows with the already-updated fr workflow and reducing pin drift across translation pipelines.
Changes:
- Updated the
QuantEcon/action-translationaction pin from@v0.16.1to@v0in the Simplified Chinese sync workflow. - Updated the
QuantEcon/action-translationaction pin from@v0.16.1to@v0in the Farsi sync workflow.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/sync-translations-zh-cn.yml | Switches the translation engine action pin to floating @v0 for zh-cn sync runs. |
| .github/workflows/sync-translations-fa.yml | Switches the translation engine action pin to floating @v0 for fa sync runs. |
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.
Completes the pin migration this repo started for French in #581.
Translation happens in the source repo's sync workflow, not in the target — so these two pins govern which engine version actually translates
faandzh-cncontent. They were still on@v0.16.1, two releases behind. That asymmetry is exactly what let French syncs keep stripping non-breaking spaces for four days after the target-side migration in .fr#10 had supposedly fixed it; #581 closed that gap for French and this closes it for the other two.Why floating
@v0The policy settled in QuantEcon/project-translation#9: it is the action's own documented convention (19 occurrences in its docs against a single exact pin), its floating tags are well maintained, and development tempo is fast enough that hand-bumping reliably lags the releases worth having. The residual "0.x may break" risk is mitigated not by the pin but by sync output landing as a PR a human reviews before merge.
What this completes
With these two, all nine translation workflow pins across the programming trio track
@v0:@v0(#581)@v0(this PR)@v0(this PR)@v0@v0(fa#137)@v0(zh-cn#73)The practical effect is that future engine releases reach production on merge, rather than needing a rollout PR round each time — which matters because a queue of silent-corruption fixes is being worked in
action-translationright now (#120).Part of Stage 1 of the translation program work plan. See QuantEcon/project-translation#9.
🤖 Generated with Claude Code