Repository navigation
Conversation
The runners were forcing checkout, upload-artifact, download-artifact and setup-java onto Node 24 because their v4 line targets the deprecated Node 20 runtime. Move to the current majors: checkout v7, upload-artifact v7, download-artifact v8 and setup-java v6. The v5 line of the artifact actions still defaults to Node 20, so it would not have cleared the warning.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Os runners estavam forçando
checkout,upload-artifact,download-artifactesetup-javapara Node 24, porque a linha v4 dessas actions ainda mira o runtime Node 20, descontinuado.actions/checkoutactions/upload-artifactactions/download-artifactactions/setup-javaPor que não v5
A v5 de
upload-artifactedownload-artifactsó tem suporte preliminar a Node 24 — por padrão ainda roda em Node 20, então não limparia o aviso. Só a v6 em diante muda o runtime de fato.Breaking changes avaliadas
download-artifactv5publishbaixa todos os artefatos, semartifact-idsdownload-artifactv8merge-multiplesegue existindo e os artefatos são zips normaisupload-artifactv7archive, defaulttruesetup-javav6jdkFilerenomeado parajdk-filecheckoutv7pull_request_target/workflow_runRunner mínimo exigido: 2.327.1 (os hospedados pelo GitHub já estão acima).
Validação
CI verde no push da
dev, com zero ocorrências de "Node.js 20 is deprecated" no log. Odownload-artifact@v8só é exercitado no jobpublishdo release, então sua validação real acontece no próximo release.