git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] GitHub Actions: update to checkout@v4

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 3, 2024, 17:18 UTC
Message-ID
<xmqqh6ipsby4.fsf@gitster.g>
In-Reply-To
<CADCFv=4Gjh5B6RFF3P--FO9T7R+uGg2dyN8hT4VR0yJtJt-UsA@mail.gmail.com>
Óscar Domínguez Celada <dominguez.celada@gmail.com> writes:
Show 5 quoted lines
> 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.

Previous: Óscar Domínguez Celada
Message 5 of 5 in “GitHub Actions update”
  1. 0/2 GitHub Actions updateJunio C Hamano, Feb 2, 2024
  2. 1/2 GitHub Actions: update to checkout@v4Junio C Hamano, Feb 2, 2024
  3. 2/2 GitHub Actions: update to github-script@v7Junio C Hamano, Feb 2, 2024
  4. Óscar Domínguez CeladaFeb 3, 2024
  5. Junio C HamanoFeb 3, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.