Bundled punycode DEP0040 warning persists in v5 — @actions/artifact ^2.1.8 needs upgrade
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 76/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Tranquilla
- Stack tecnologico
- javascript
- Ambito
- devops
Direzione di ricerca
Inizia da actions/deploy-pages/package.json e dalla riga della dipendenza @actions/artifact, quindi esamina il dist/index.js incluso e il processo di build ncc a cui si fa riferimento. Aggiorna la dipendenza a una versione che contenga la correzione per punycode, ricompila dist/ e verifica che l’avviso DEP0040 non venga più emesso prima di preparare la release v5.0.1 o v5.1.0 richiesta.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
actions/[email protected] (released 2026-03-25, latest) still emits a DEP0040 punycode DeprecationWarning in every "Deploy to GitHub Pages" step. This persists even with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true, because the warning isn't from the Node version mismatch — it's from a transitive dependency in the bundled action that loads Node's deprecated punycode module at startup.
This is the "won't go away though" warning that @jaredthivener noted in #410 (the Node 24 support issue, which is essentially solved by v5).
Root cause
actions/deploy-pages/package.json pins:
"dependencies": {
"@actions/artifact": "^2.1.8",
...
}
@actions/artifact v2.x predates the punycode fix. The punycode fix was shipped in @actions/artifact v6.0.0 (December 2025), and actions/upload-artifact itself moved to it in actions/upload-artifact#744.
The package.json line for @actions/artifact hasn't been touched since 2024-07-15 (commit 479a2d95).
Trace
A diagnose run with NODE_OPTIONS=--trace-deprecation:
(node:6488) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
at node:punycode:7:10
at BuiltinModule.compileForInternalLoader (node:internal/bootstrap/realm:398:7)
at BuiltinModule.compileForPublicLoader (node:internal/bootstrap/realm:337:10)
at loadBuiltinModule (node:internal/modules/helpers:125:7)
at loadBuiltinWithHooks (node:internal/modules/cjs/loader:1202:15)
at Module._load (node:internal/modules/cjs/loader:1293:48)
at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
at Module.require (node:internal/modules/cjs/loader:1556:12)
at require (node:internal/modules/helpers:152:16)
at Object.85477 (/home/runner/work/_actions/actions/deploy-pages/v5/external node-commonjs "punycode":1:1)
The bundled module ID 85477 resolves to a node-commonjs "punycode" external in the ncc-built dist/index.js of actions/deploy-pages@v5.
Ask
Bump @actions/artifact from ^2.1.8 to ^6.x (or whatever current major has the punycode fix). After the bump, rebuild the dist/ bundle with ncc and tag a v5.0.1 / v5.1.0.
This would silence the warning for every consumer of actions/deploy-pages@v5 without requiring them to wait for upstream Node version migrations or pin SHAs.
Related
- #410 — "Support Node.js 24" (the parent thread; the Node 24 part was solved in v5, but the punycode subwarning is a different transitive-dep issue)
- actions/upload-artifact#744 — the original
@actions/artifactv6.0.0 punycode fix - actions/upload-pages-artifact#142 — same root cause, different action — sister issue I just filed for the upload side
Workaround
There is no clean workaround. FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true doesn't help (the warning isn't about Node version). SHA-pinning to current main doesn't help either, because main is cd2ce8fc from 2026-03-24, which is exactly what v5.0.0 was tagged from on 2026-03-25 — there's no newer commit to pin to. The fix must come from a maintainer-side @actions/artifact bump.
- Lingua principale
- JavaScript
- Stelle
- 967
- Fork
- 147
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di actions/deploy-pages
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
actions/deploy-pages#454 · 1 commento ·
-
Intermittent "No artifacts named github-pages" when deploy-pages runs right after upload-pages-artifact in the same jobForse già presa @neilime l’ha presa 7 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
actions/deploy-pages#451 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
actions/deploy-pages#435 · 3 commenti ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 65/100
actions/deploy-pages#434 · 3 commenti · 1 reazione ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 48/100
actions/deploy-pages#418 · 19 commenti · 12 reazioni ·
Tutte le issue di actions/deploy-pages
Issue simili
-
type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
ai-amazon-bedrock: a tool result that isn't a JSON object fails the next requestForse già presa @effect-bot l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
I maintainer di solito rispondono entro 1 giorno
-
[bug] Toolchain versions from `.prototools` are not inherited when moon runs from a subdirectoryAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
Edit: Tele1 Logo [SV]Apertacheck:passed logos:edit
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno