v5 emits Node DEP0040 punycode deprecation warning on successful deployments
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, node.js
Research direction
Start by tracing the dependency that imports Node's core punycode module, then inspect the generated dist/ artifact. Add the requested Node 24 smoke test and run the deployment workflow or equivalent checks. Done means a successful deployment no longer emits DEP0040 and the generated dist/ is updated.
Written by the indexing model from the issue text.
Description
What happened
A normal successful actions/deploy-pages@v5 invocation emits:
(node:...) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
Public reproduction: the Deploy Pages artifact step in https://github.com/link-assistant/formal-ai/actions/runs/29463393707.
Minimal workflow
- uses: actions/deploy-pages@v5
with:
token: ${{ github.token }}
Suggested fix
Update the dependency that imports Node core punycode, regenerate dist/, and add a Node 24 smoke test that fails on DEP0040. Successful deployments should not require consumers to suppress runtime warnings.
- Dominant language
- JavaScript
- Stars
- 967
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from actions/deploy-pages
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
actions/deploy-pages#454 · 1 comment ·
-
Intermittent "No artifacts named github-pages" when deploy-pages runs right after upload-pages-artifact in the same jobPossibly taken @neilime claimed this 7 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
actions/deploy-pages#451 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
actions/deploy-pages#435 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
actions/deploy-pages#418 · 19 comments · 12 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
actions/deploy-pages#416 ·
All issues in actions/deploy-pages
Similar issues
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
ai-amazon-bedrock: a tool result that isn't a JSON object fails the next requestPossibly taken @effect-bot claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
[bug] Toolchain versions from `.prototools` are not inherited when moon runs from a subdirectoryOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
check:passed logos:edit
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day