| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
per discussion at #51356 (comment), targeting v21.x-staging |
Sorry, something went wrong.
Before approving, do we have some docs about reverting changes? Should we actually revert or create a new commit with the change?
There was a problem hiding this comment.
According to reverting commits docs, you only need to include Fixes: #PR in the PR message, can you update that?
Sorry, something went wrong.
Sorry, something went wrong.
No need to modify the commit message for that, you can edit the PR description and it will be picked up by ncu and added to the commit message upon landing. But not sure if we use the same process for landing PRs on staging branches. |
Sorry, something went wrong.
There was a problem hiding this comment.
Why revert it only to v21.x but not main?
Sorry, something went wrong.
Done |
Sorry, something went wrong.
|
@RafaelGSS Because the esm package is archived and will never be fixed. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
@jeremymeng rebased |
Sorry, something went wrong.
This reverts commit 95b1989. It appears that the workaround is still needed: issue nodejs#51081
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes: #51081