rusackas opened a new pull request, #45584: URL: https://github.com/apache/superset/pull/45584
### SUMMARY Follow-up to #45583: adds a scheduled job so locale `.po` catalogs stop silently drifting behind `messages.pot` between manual catch-ups. `check_pot_drift.py` already guarantees `messages.pot` matches source on every PR, but a PR that adds a translatable string is only required to regenerate `messages.pot` — propagating the new entries into every locale catalog via `pybabel update` is a separate, unenforced step. `check_translation_regression.py` can't catch the gap either: it only compares relative translated/fuzzy counts between a base ref and a PR, so any pre-existing drift cancels out on both sides and never fails. This adds `.github/workflows/sync-translation-catalogs.yml`: - Runs weekly (Mondays 06:00 UTC) and on `workflow_dispatch`. - Runs `scripts/translations/babel_update.sh` against current `master`. - If that produces a diff under `superset/translations`, commits it on `chore/sync-translation-catalogs-automated` and opens a PR (or updates the existing one if last week's is still open), using the default `GITHUB_TOKEN` with `contents: write` + `pull-requests: write` — no new third-party action, mirroring the pattern already used by `bump-python-package.yml`. - A human still reviews and merges every PR; nothing is pushed straight to `master`. This matches ASF Infra's GitHub Actions policy, which restricts automated services from pushing directly to a release-subject branch without prior Infra authorization, but doesn't restrict a bot opening a PR for review (the same category Dependabot itself falls into, and which ASF requires enabling on every repo). ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF N/A ### TESTING INSTRUCTIONS - `zizmor`/pre-commit pass on the new workflow file. - The underlying `babel_update.sh` + diff/commit logic was exercised locally against current `master`, producing the catch-up in #45583 — that's the same diff this job would commit on its first scheduled run. The workflow definition itself hasn't run in GitHub Actions yet (it only runs from a branch GitHub recognizes); worth triggering once manually via `workflow_dispatch` after merge to confirm the PR-open/update path end-to-end, then it should be a no-op most weeks. ### ADDITIONAL INFORMATION - [ ] Has associated issue: - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351)) - [ ] Migration is atomic, supports rollback & is backwards-compatible - [ ] Confirm DB migration upgrade and downgrade tested - [ ] Runtime estimates and downtime expectations provided - [ ] Introduces new feature or API - [ ] Removes existing feature or API 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
