Donkie e175708b3e fix(ci): diff PRs from the merge base in guard-translations ...

The guard compared the base branch tip against the PR head directly, so
every commit that landed on master after a PR forked counted as one of
that PR every time it re-ran. Merging a Weblate sync therefore failed
unrelated PRs with client_v2/locales/sv/common.json in the offending
list, and the only way out was rebasing a PR that had never touched a
translation file.

Diffing BASE...HEAD resolves the merge base first, which is what "the
changes this PR makes" means, and it stays right however far master
moves on. Verified against PR 1001: the old form flags sv, the new form
passes, and a real hand-edit of sv is still caught.

2026-08-01 22:11:42 +02:00

..

apidocs.yml

CI fixes

2026-01-18 16:55:31 +01:00

ci.yml

Build on Node 24, which is not end-of-life

2026-07-31 09:00:16 +02:00

guard-translations.yml

fix(ci): diff PRs from the merge base in guard-translations

2026-08-01 22:11:42 +02:00

issue-manager.yml

ci: bump issue-manager to 0.8.1 and fix waiting delay

2026-07-24 10:22:08 +02:00

trigger-release.yml

Build on Node 24, which is not end-of-life

2026-07-31 09:00:16 +02:00

weblate-automerge.yml

Point the translation workflows at client_v2, close the legacy client

2026-07-31 10:35:01 +02:00