RFR: 8324723: GHA: Upgrade some actions to avoid deprecated Node 16 [v2]

[Jaikiran Pai]

On Fri, 26 Jan 2024 19:33:49 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

>> Current GHA runs produce lots of warnings:
>> 
>> Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache at v3, actions/download-artifact at v3, actions/upload-artifact at v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
>> 
>> We can upgrade to new actions to get the Node20.
>> 
>> Release/migration notes:
>> https://github.com/actions/cache#whats-new
>> https://github.com/actions/upload-artifact/blob/main/docs/MIGRATION.md
>> https://github.com/actions/download-artifact/blob/main/docs/MIGRATION.md
>> https://github.com/actions/github-script#breaking-changes
>> 
>> There is also msys2/setup-msys2, which was pinned by [JDK-8310259](https://bugs.openjdk.org/browse/JDK-8310259). We need at least 2.21.0 to get Node 20:
>> https://github.com/msys2/setup-msys2/blob/main/CHANGELOG.md. I think we can unpin msys2 at this point.
>> 
>> I don't think any of the migration problems outlined in those notes apply to our workflows.
>> 
>> Additional testing:
>>  - [x] 3x GHA with cleaned caches
>>  - [x]  3x GHA with populated caches (default)
>
> Aleksey Shipilev has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Also update github-script

Hello Severin,

> Not really sure how to test the msys2 pinning issue...

I think as long as the GitHub actions jobs complete successfully, that should be enough. However, it's not a guarantee that the issue won't happen again (previously, we have had a case where it worked for a few hours or maybe a day when Java 17 was used https://bugs.openjdk.org/browse/JDK-8309934 before it started failing again). If it does happen again, in a subsequent PR, we can always pin it back and spend some more time investigating what's going on.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/17572#issuecomment-1914394646