From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: Aaron Conole <aconole@redhat.com>,
Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [PATCH 2/2] ci: update to new API for step outputs in GHA
Date: Mon, 17 Oct 2022 16:01:38 +0200 [thread overview]
Message-ID: <CAJFAV8wRvojMr88fTOuf2wzCkSmSS58Cr4hbtrkcfG3o=cFMXQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ytFpoTjSkvicK7_RQo6PJp1mxV+qLgv3=zLEn3uv1N3Q@mail.gmail.com>
On Wed, Oct 12, 2022 at 6:53 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Wed, Oct 12, 2022 at 6:30 PM David Marchand
> <david.marchand@redhat.com> wrote:
> >
> > GitHub actions deprecated use of set-output, replaced with
> > GITHUB_OUTPUT.
It is worth mentionning the deprecation announce:
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
> >
> > Note: we still have some warnings, as of today, because of
> > actions/cache@v3 which did not migrate yet.
>
> For the record, the changes in actions/cache@v3 are pushed in its main
> branch, but are not released yet.
> https://github.com/actions/cache/commit/b9c8bfe4426d
The fixes have been released under v3.0.11.
So with this series applied, there is no warning remaining, for now.
--
David Marchand
next prev parent reply other threads:[~2022-10-17 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 16:29 [PATCH 0/2] GitHub Actions configuration fixes David Marchand
2022-10-12 16:29 ` [PATCH 1/2] ci: bump versions of actions in GHA David Marchand
2022-10-12 16:29 ` [PATCH 2/2] ci: update to new API for step outputs " David Marchand
2022-10-12 16:53 ` David Marchand
2022-10-17 14:01 ` David Marchand [this message]
2022-11-14 10:44 ` [PATCH 0/2] GitHub Actions configuration fixes David Marchand
2022-11-14 20:53 ` David Marchand
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='CAJFAV8wRvojMr88fTOuf2wzCkSmSS58Cr4hbtrkcfG3o=cFMXQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).