From: Junio C Hamano <gitster@pobox.com>
To: "Óscar Domínguez Celada" <dominguez.celada@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] GitHub Actions: update to checkout@v4
Date: Sat, 03 Feb 2024 09:18:59 -0800 [thread overview]
Message-ID: <xmqqh6ipsby4.fsf@gitster.g> (raw)
In-Reply-To: <CADCFv=4Gjh5B6RFF3P--FO9T7R+uGg2dyN8hT4VR0yJtJt-UsA@mail.gmail.com> ("Óscar Domínguez Celada"'s message of "Sat, 3 Feb 2024 12:39:00 +0100")
Óscar Domínguez Celada <dominguez.celada@gmail.com> writes:
> I am adding non-html e-mail reply to keep track in git@vger.kernel.org:
>
> The switch to checkout@v4 for GitHub Actions looks good to me. I
> wonder if we should be updating other actions to v4 so they start
> using Node 20:
No need to wonder. I only noticed the ones involved in the main CI
job that triggered the warnings, and dealt only with the "easy" ones
;-) The primary reason why I CC'ed you was because I hoped you knew
better about the "container jobs are pinned at checkout@v1", which I
left as-is.
Help in updating other actions to newer versions, if needed, is greatly
appreciated.
next prev parent reply other threads:[~2024-02-03 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 20:39 [PATCH 0/2] GitHub Actions update Junio C Hamano
2024-02-02 20:39 ` [PATCH 1/2] GitHub Actions: update to checkout@v4 Junio C Hamano
[not found] ` <CADCFv=5=uwp_NVpndTYFiRRK4hEwmMdA2At80cXuS91V5mKN2A@mail.gmail.com>
2024-02-03 11:39 ` Óscar Domínguez Celada
2024-02-03 17:18 ` Junio C Hamano [this message]
2024-02-02 20:39 ` [PATCH 2/2] GitHub Actions: update to github-script@v7 Junio C Hamano
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=xmqqh6ipsby4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dominguez.celada@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.