-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci(l10n): bump Actions versions to avoid Node.js 16 deprecation warnings #749
Conversation
Errors and warnings found by git-po-helper in workflow #534:
|
Umm. I would argue that this is for git-l10n... I guess that we'll need to change this condition? |
…rship The PR checks would otherwise fail if someone opens a PR to adjust the l10n GitHub workflow, as I did over here: git-l10n/git-po#749 Signed-off-by: Johannes Schindelin <[email protected]>
Errors and warnings found by git-po-helper in workflow #535:
|
Errors and warnings found by git-po-helper in workflow #536:
|
Errors and warnings found by git-po-helper in workflow #538:
|
Errors and warnings found by git-po-helper in workflow #540:
|
Errors and warnings found by git-po-helper in workflow #542:
|
Errors and warnings found by git-po-helper in workflow #544:
|
9e9e642
to
c5f67b5
Compare
Errors and warnings found by git-po-helper in workflow #546:
|
c5f67b5
to
ef79263
Compare
Errors and warnings found by git-po-helper in workflow #548:
|
This avoids the "Node.js 16 Actions are deprecated" warnings. Original-commits-by: dependabot[bot] <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
ef79263
to
14a4f26
Compare
Errors and warnings found by git-po-helper in workflow #550:
|
This PR requires git-l10n/git-po-helper#18 to be merged first, to avoid all those incorrect |
14a4f26
to
6032aee
Compare
@jiangxin please review. |
LGTM, will merge. |
Please help to review pull request #757 . |
This avoids the "Node.js 16 Actions are deprecated" warnings.
Since this workflow only runs in the l10n forks of
git/git
, it would be inappropriate to submit this patch to the Git mailing list for review, and I deem this the correct place to offer my contribution.