ci: bump pnpm/action-setup para v5 (Node.js 24)#30
Merged
Conversation
GitHub deprecou Node.js 20; v4 ainda usa Node 20 e dispara warning. v5.0.0 apenas atualiza o runtime para Node 24 (sem mudar pnpm bundled, mantendo compat com packageManager pnpm@9.x).
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
1 participant
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.
Resumo
pnpm/action-setupde@v4para@v5em todos os workflows.packageManager: pnpm@9.x).Por quê
GitHub deprecou Node.js 20 nos runners;
pnpm/action-setup@v4ainda roda em Node 20 e dispara warning em todo job. A partir de 2026-06-02 o runner força Node 24 por padrão; em 2026-09-16 Node 20 é removido. Resolvendo agora antes de quebrar.Notas:
packageManager: pnpm@9.15.9.Test plan