Skip to content
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

process: remove support for undocumented symbol #56552

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Jan 10, 2025

The symbol was undocumented in #56517, but left in the code to avoid a breaking change. This PR makes the breaking change, I suggest we skip landing it on 23.x and directly backport it to 22.x so that release line only receive support for the documented symbol.

@aduh95 aduh95 added backport-requested-v22.x PRs awaiting manual backport to the v22.x-staging branch. 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 Jan 10, 2025
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. process Issues and PRs related to the process subsystem. labels Jan 10, 2025
Copy link

codecov bot commented Jan 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.17%. Comparing base (3946f16) to head (58cb88e).
Report is 8 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #56552      +/-   ##
==========================================
+ Coverage   89.16%   89.17%   +0.01%     
==========================================
  Files         662      662              
  Lines      191751   191753       +2     
  Branches    36900    36904       +4     
==========================================
+ Hits       170972   171000      +28     
+ Misses      13635    13630       -5     
+ Partials     7144     7123      -21     
Files with missing lines Coverage Δ
lib/internal/process/per_thread.js 99.33% <100.00%> (+<0.01%) ⬆️

... and 28 files with indirect coverage changes

@richardlau
Copy link
Member

richardlau commented Jan 10, 2025

The symbol was undocumented in #56517, but left in the code to avoid a breaking change. This PR makes the breaking change, I suggest we skip landing it on 23.x and directly backport it to 22.x so that release line only receive support for the documented symbol.

I'm confused by this. Why break 22 but not 23? (Why would we break 22 at all?)

@lpinca
Copy link
Member

lpinca commented Jan 10, 2025

If I understand correctly nothing breaks on 22 as #56400 will not be backported (#56517 should also not be backported), so this will only add support for the correct symbol (without documentation)?

@aduh95
Copy link
Contributor Author

aduh95 commented Jan 10, 2025

What I'm suggesting is we backport all three PRs, so what gets released on 22.x is the correct symbols with documentation, and not the undocumented ones. As Luigi said, it would not break 22.x users since nothing has landed for them atm.

@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Jan 10, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jan 10, 2025
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@aduh95 aduh95 added the commit-queue Add this label to land a pull request using GitHub Actions. label Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. backport-requested-v22.x PRs awaiting manual backport to the v22.x-staging branch. commit-queue Add this label to land a pull request using GitHub Actions. dont-land-on-v23.x PRs that should not land on the v23.x-staging branch and should not be released in v23.x. needs-ci PRs that need a full CI run. process Issues and PRs related to the process subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants