]> git.ipfire.org Git - thirdparty/git.git/commit
l10n: bump mshick/add-pr-comment from v2 to v3
authorJohannes Schindelin <johannes.schindelin@gmx.de>
Thu, 30 Apr 2026 07:35:00 +0000 (07:35 +0000)
committerJunio C Hamano <gitster@pobox.com>
Thu, 30 Apr 2026 09:21:55 +0000 (18:21 +0900)
commit4a6ed9d09f9346f24c15c408b8eb005c3133fd5b
tree0fa3b13cedf4621a72a4921647f790333030812b
parent7e6ede6ce11430d2c6f314005926d91f0a68c2f8
l10n: bump mshick/add-pr-comment from v2 to v3

The l10n workflow uses `mshick/add-pr-comment` to post git-po-helper
reports as comments on translation pull requests. It was still pinned
to v2, which runs on Node.js 20. GitHub is phasing out the Node.js 20
runtime on Actions runners, so staying on v2 will eventually cause the
"Create comment in pull request for report" step to fail.

The sole breaking change in v3 is the switch from Node.js 20 to
Node.js 24 (https://github.com/mshick/add-pr-comment/releases/tag/v3.0.0).
The action's inputs and outputs are unchanged, so the upgrade is a
drop-in replacement. Subsequent v3.x releases added new opt-in
features (message truncation, retry with exponential backoff, file
attachments, commit comment support, "delete on status") but none of
them affect existing callers that do not opt in.

See also:

- Changelog: https://github.com/mshick/add-pr-comment/blob/main/CHANGELOG.md
- Compare: https://github.com/mshick/add-pr-comment/compare/v2...v3

Pointed-out-by: Christoph GrĂ¼ninger <foss@grueninger.de>
Assisted-by: Claude Opus 4.6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
.github/workflows/l10n.yml