Skip to content

doc: correct status of require(esm) warning in v20 changelog #57529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 19, 2025

Conversation

joyeecheung
Copy link
Member

@joyeecheung joyeecheung commented Mar 18, 2025

The backported patches already include the commit that disables the warning unless --trace-require-module is explicitly used. Correct the changelog to match the status.

Fixes: #57517

The backported patches already include the commit that disables
the warning unless `--trace-require-module` is explicitly used.
Correct the changelog to match the status.
@nodejs-github-bot nodejs-github-bot added the release Issues and PRs related to Node.js releases. label Mar 18, 2025
@joyeecheung
Copy link
Member Author

cc @marco-ippolito

@joyeecheung joyeecheung added the fast-track PRs that do not need to wait for 48 hours to land. label Mar 18, 2025
Copy link
Contributor

Fast-track has been requested by @joyeecheung. Please 👍 to approve.

@joyeecheung joyeecheung added the commit-queue Add this label to land a pull request using GitHub Actions. label Mar 19, 2025
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Mar 19, 2025
@nodejs-github-bot nodejs-github-bot merged commit fe5817e into nodejs:main Mar 19, 2025
27 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in fe5817e

@joyeecheung
Copy link
Member Author

@aduh95 aduh95 added dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. lts-watch-v20.x PRs that may need to be released in v20.x dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v23.x PRs that should not land on the v23.x-staging branch and should not be released in v23.x. labels Mar 22, 2025
aduh95 pushed a commit that referenced this pull request Mar 22, 2025
The backported patches already include the commit that disables
the warning unless `--trace-require-module` is explicitly used.
Correct the changelog to match the status.

PR-URL: #57529
Fixes: #57517
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
RafaelGSS pushed a commit that referenced this pull request Apr 1, 2025
The backported patches already include the commit that disables
the warning unless `--trace-require-module` is explicitly used.
Correct the changelog to match the status.

PR-URL: #57529
Fixes: #57517
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
RafaelGSS pushed a commit that referenced this pull request Apr 1, 2025
The backported patches already include the commit that disables
the warning unless `--trace-require-module` is explicitly used.
Correct the changelog to match the status.

PR-URL: #57529
Fixes: #57517
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. dont-land-on-v23.x PRs that should not land on the v23.x-staging branch and should not be released in v23.x. fast-track PRs that do not need to wait for 48 hours to land. lts-watch-v20.x PRs that may need to be released in v20.x release Issues and PRs related to Node.js releases.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

v20.19.0 release notes - outdated messaging
6 participants