chore: track action-translation @v0 in the fr sync workflow#581
Merged
Conversation
The fr target repo adopted the floating @v0 pin in QuantEcon/lecture-python-programming.fr#10; this brings the source-side sync workflow in line so fr syncs pick up v0.17.0 (deterministic typography on the sync write path, review-comment dedupe) and future v0.x releases without manual bumps. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the French translation sync workflow to track the QuantEcon/action-translation floating major tag (@v0), aligning the source-side workflow with the target repo’s configuration so future v0.x improvements are picked up without manual version bumps.
Changes:
- Switch
QuantEcon/action-translationfrom@v0.16.1to the floating@v0tag in the French sync workflow.
mmcky
added a commit
that referenced
this pull request
Jul 21, 2026
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>
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.
The fr target repo's review and rebase workflows adopted the floating
@v0pin in QuantEcon/lecture-python-programming.fr#10. This brings the source-sidesync-translations-fr.ymlin line, so fr syncs run v0.17.0 — whose sync write path preserves French non-breaking spaces (QuantEcon/action-translation#97) and dedupes review comments (QuantEcon/action-translation#96) — and pick up future v0.x releases without manual bumps.Not touched here:
sync-translations-zh-cn.ymlandsync-translations-fa.ymlremain pinned at@v0.16.1. Happy to follow up with the same change for those if the floating pin is the fleet convention.🤖 Generated with Claude Code