v5 emits Node DEP0040 punycode deprecation warning on successful deployments

Open
#434 3 comments 1 reaction 0 assignees View on GitHub

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
Domain
ci-cd, devops

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/deploy-pages

All issues in actions/deploy-pages

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.