kdmukai 596528f117 Give the hash-locked l10n install its own pip invocation ...

pip enables hash-checking for an entire invocation the moment any
requirement in it carries a hash, and then demands hashes for
everything else in that invocation. The combined install line mixed
requirements-l10n.txt with two unhashed files and an editable install,
so it fails now that the l10n pins are hash-locked -- and
requirements.txt cannot simply join hash mode, because hash-checking
rejects its git-pinned entries outright.

Splitting the install keeps the l10n file's hashes enforced while the
other files continue to install unhashed. The comment above the
split line records why it exists, so it doesn't get folded back into
the combined line and break CI later.

2026-08-19 19:03:59 -05:00

..

build.yml

fix build github action after version addition

2026-07-22 15:42:28 -04:00

tests.yml

Give the hash-locked l10n install its own pip invocation

2026-08-19 19:03:59 -05:00