Re: [PATCH 1/4] ci: use a newer `github-script` version
- From
Taylor Blau <me@ttaylorr.com>
- Date
- Dec 7, 2022, 22:22 UTC
- Message-ID
- <Y5ESKYvOyrnbCV+B@nand.local>
- In-Reply-To
- <472481561f03900fb519065d88ae8af910bea794.1670423680.git.gitgitgadget@gmail.com>
On Wed, Dec 07, 2022 at 02:34:37PM +0000, Johannes Schindelin via GitGitGadget wrote:
Show 11 quoted lines
> From: Johannes Schindelin <johannes.schindelin@gmx.de> > > The old version we currently use runs in node.js v12.x, which is being > deprecated in GitHub Actions. The new version uses node.js v16.x. > > Incidentally, this also avoids the warning about the deprecated > `::set-output::` workflow command because the newer version of the > `github-script` Action uses the recommended new way to specify outputs. > > Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> > Signed-off-by: Taylor Blau <me@ttaylorr.com>
It took me a second to remember why my S-o-b was here, but it looks like this is from when I queued this patch in [1], which is on 'master' as of 63357b79c9 (ci: use a newer `github-script` version, 2022-11-08).
So having my S-o-b here is definitely OK (since I was the one who put it there in the first place!), but I don't think we need to re-queue this patch, unless it was reverted out in the meantime (which it doesn't appear to be).
Thanks, Taylor
[1]: https://lore.kernel.org/git/Y2q9723uEtfkJrah@nand.local/