From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Christoph Grüninger" <foss@grueninger.de>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: [PATCH v3 6/6] l10n: bump mshick/add-pr-comment from v2 to v3
Date: Thu, 30 Apr 2026 07:35:00 +0000 [thread overview]
Message-ID: <b9ccb66405c887812a3dd5791b343aed6c15a15f.1777534500.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2097.v3.git.1777534500.gitgitgadget@gmail.com>
From: Johannes Schindelin <johannes.schindelin@gmx.de>
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>
---
.github/workflows/l10n.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.github/workflows/l10n.yml b/.github/workflows/l10n.yml
index 95e55134bd..114a12a9e5 100644
--- a/.github/workflows/l10n.yml
+++ b/.github/workflows/l10n.yml
@@ -92,7 +92,7 @@ jobs:
cat git-po-helper.out
exit $exit_code
- name: Create comment in pull request for report
- uses: mshick/add-pr-comment@v2
+ uses: mshick/add-pr-comment@v3
if: >-
always() &&
github.event_name == 'pull_request_target' &&
--
gitgitgadget
prev parent reply other threads:[~2026-04-30 7:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 12:41 [PATCH 0/4] ci: GitHub Actions updates (brought to you by Dependabot) Johannes Schindelin via GitGitGadget
2026-04-21 12:41 ` [PATCH 1/4] ci: bump microsoft/setup-msbuild from v2 to v3 Johannes Schindelin via GitGitGadget
2026-04-21 12:41 ` [PATCH 2/4] ci: bump actions/{upload,download}-artifact to v7 and v8 Johannes Schindelin via GitGitGadget
2026-04-21 12:41 ` [PATCH 3/4] ci: bump actions/github-script from v8 to v9 Johannes Schindelin via GitGitGadget
2026-04-21 12:41 ` [PATCH 4/4] ci: bump actions/checkout from v5 to v6 Johannes Schindelin via GitGitGadget
2026-04-25 10:58 ` [PATCH v2 0/5] ci: GitHub Actions updates (brought to you by Dependabot) Johannes Schindelin via GitGitGadget
2026-04-25 10:58 ` [PATCH v2 1/5] ci: bump microsoft/setup-msbuild from v2 to v3 Johannes Schindelin via GitGitGadget
2026-04-25 10:58 ` [PATCH v2 2/5] ci: bump actions/{upload,download}-artifact to v7 and v8 Johannes Schindelin via GitGitGadget
2026-04-25 10:58 ` [PATCH v2 3/5] ci: bump actions/github-script from v8 to v9 Johannes Schindelin via GitGitGadget
2026-04-25 10:58 ` [PATCH v2 4/5] ci: bump actions/checkout from v5 to v6 Johannes Schindelin via GitGitGadget
2026-04-25 10:58 ` [PATCH v2 5/5] l10n: bump mshick/add-pr-comment from v2 to v3 Johannes Schindelin via GitGitGadget
2026-04-30 7:34 ` [PATCH v3 0/6] ci: GitHub Actions updates (brought to you by Dependabot) Johannes Schindelin via GitGitGadget
2026-04-30 7:34 ` [PATCH v3 1/6] ci: bump microsoft/setup-msbuild from v2 to v3 Johannes Schindelin via GitGitGadget
2026-04-30 7:34 ` [PATCH v3 2/6] ci: bump actions/{upload,download}-artifact to v7 and v8 Johannes Schindelin via GitGitGadget
2026-04-30 7:34 ` [PATCH v3 3/6] ci: bump actions/github-script from v8 to v9 Johannes Schindelin via GitGitGadget
2026-04-30 7:34 ` [PATCH v3 4/6] ci: bump actions/checkout from v5 to v6 Johannes Schindelin via GitGitGadget
2026-04-30 7:34 ` [PATCH v3 5/6] ci: bump git-for-windows/setup-git-for-windows-sdk from v1 to v2 Johannes Schindelin via GitGitGadget
2026-04-30 7:35 ` Johannes Schindelin via GitGitGadget [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9ccb66405c887812a3dd5791b343aed6c15a15f.1777534500.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=foss@grueninger.de \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox